fix: (db) add limit param to memory retrieval across adapters

[augchan42]

• Add limit parameter to getMemoriesByRoomIds in SQLite adapter
• Add limit parameter to getMemoriesByRoomIds in SQLjs adapter
• Add limit parameter to getMemoriesByRoomIds in PGLite adapter
• Add limit parameter to getMemoriesByRoomIds in Supabase adapter
• Fix query parameter ordering in SQLjs adapter
• Add consistent DESC ordering across all adapters

Without this, all memories are retrieved for that room since the limit being passed from getRecentInteractions in the core runtime is ignored silently:

    // Check the existing memories in the database
            return this.messageManager.getMemoriesByRoomIds({
                // filter out the current room id from rooms
                roomIds: rooms.filter((room) => room !== roomId),
                limit: 20,
            });

Closes #2253

Discord username: hosermage

[augchan42]

Oh, the postgres adapter does already have limit support, so those using postgres do not experience this issue.
in packages/adapter-postgres/src/index.ts, getMemoriesByRoomIds function:

            // Add sorting, and conditionally add LIMIT if provided
            query += ` ORDER BY "createdAt" DESC`;
            if (params.limit) {
                query += ` LIMIT $${queryParams.length + 1}`;
                queryParams.push(params.limit.toString());
            }

[shakkernerd]

Oh, the postgres adapter does already have limit support, so those using postgres do not experience this issue. in packages/adapter-postgres/src/index.ts, getMemoriesByRoomIds function:

            // Add sorting, and conditionally add LIMIT if provided
            query += ` ORDER BY "createdAt" DESC`;
            if (params.limit) {
                query += ` LIMIT $${queryParams.length + 1}`;
                queryParams.push(params.limit.toString());
            }

Yes, the limit implementation was missing in the sqlite adapter and most likely other too.

[shakkernerd]

Good one!