fix(memory): honor custom table names in AdvancedSQLiteSession#2694
Merged
fix(memory): honor custom table names in AdvancedSQLiteSession#2694
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request fixes
AdvancedSQLiteSessionso it consistently respects configuredsessions_tableandmessages_tablenames. The previous implementation inherited custom table-name support fromSQLiteSessionbut still hardcodedagent_messagesandagent_sessionsin schema foreign keys and several branch/query paths, which caused failures such asno such table: agent_messageswhen custom names were used. This change updates those schema definitions and queries to use the configured tables and adds regression coverage for retrieval, turn browsing, content search, branch creation, and schema foreign-key metadata.for context: #2692 (comment)