feat: add foreign key relations for cascade deletes to chat tables #125
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.
Summary
This PR implements the necessary changes to handle foreign key relationships between the
ChatSessionstable and its dependent tablesConversationMessagesandWorkingMemory. This is useful if a user wants to delete a chat, we can perform a cascading deletion as defined in our schema. The FK constraint is entirely opt-in, but certain order of operations needed to change.Code changes
saveConversation()method: Ensures the chat session row is created/updated before saving messages to prevent FK constraint violations.Impact