fix: correct JSON field serialization for PostgreSQL vs SQLite#2798
Merged
os-zhuang merged 1 commit intoJul 11, 2026
Merged
Conversation
PostgreSQL native jsonb columns require all values to be valid JSON, while SQLite stores JSON as TEXT so only objects/arrays need stringification. Previously the SQLite-only path incorrectly applied to PG, and primitives in PG jsonb columns were silently rejected. Co-authored-by: Cursor <cursoragent@cursor.com>
|
@akarma-synetal is attempting to deploy a commit to the Object Stack Team on Vercel. A member of the Team first needs to authorize it. |
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
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
jsonbcolumns now correctly receiveJSON.stringifyfor all values (strings, numbers, booleans, objects)jsonbcolumns to be silently rejectedTest plan
jsonbcolumn writes with string/number/boolean values work on PostgreSQLMade with Cursor