Open
Conversation
…h both PostgreSQL and SQLite backends. The changes detect the database type at runtime and use appropriate strategies for each: - PostgreSQL: Continue using the RETURNING clause to get inserted IDs - SQLite: Track IDs before insertion and verify with a follow-up query This fixes the "not iterable" error that occurred when trying to process SQLite's integer return value from insert_many().execute().
dhars9-roche
requested review from
huany172-roche
and removed request for
dhars9-roche
Unit Test for JsonField class
huany172-roche
approved these changes
Jun 3, 2025
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
2 participants
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.
Feat: Add cross-database support for SQLite and PostgreSQL
This PR implements database-agnostic functionality allowing the application
to work seamlessly with both SQLite and PostgreSQL backends. Users can now
switch between database engines by simply changing an environment variable.
Key changes:
The application now detects the database type at runtime and adapts field
storage/retrieval accordingly, ensuring consistent behavior regardless of
the underlying database engine.
Testing: