Skip to content

fix: refuse analysis numbers PostgreSQL can't store - #266

Merged
bfabio merged 1 commit into
fix/refuse-empty-patch-valuesfrom
fix/refuse-numbers-postgresql-cannot-store
Nov 20, 2026
Merged

bfabio merged 1 commit into
fix/refuse-empty-patch-valuesfrom
fix/refuse-numbers-postgresql-cannot-store

Conversation

@bfabio

@bfabio bfabio commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

jsonb stores numbers as numeric, so a valid JSON number beyond its
range made the analysis PATCH fail with 500 on PostgreSQL while SQLite
stored it. Refuse those numbers with 422 on both databases, keeping
what a float64 can hold since that is what most clients read back.

jsonb stores numbers as numeric, so a valid JSON number beyond its
range made the analysis PATCH fail with 500 on PostgreSQL while SQLite
stored it. Refuse those numbers with 422 on both databases, keeping
what a float64 can hold since that is what most clients read back.
@bfabio
bfabio added this pull request to stack #272 November 20, 2026 10:49
@bfabio
bfabio merged commit a58b02f into main Nov 20, 2026
13 checks passed
@bfabio
bfabio deleted the fix/refuse-numbers-postgresql-cannot-store branch November 20, 2026 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant