chore: save schema integers in INTEGER SQLite columns #531
Conversation
This file contains 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
This is a test-only change (other than tweaking a comment).
If we use the ["integer" JSON Schema type][0], we should save that as an INTEGER column, not a REAL column. Both will work for many numbers, but larger integers (like `2**63`) can only be safely stored in INTEGERs. This should be a bit more reliable. As of this patch, we don't have any integer types in our schemas, so this has no effect. However, that may change as we address [upcoming issues][1]. [0]: https://json-schema.org/understanding-json-schema/reference/numeric#integer [1]: #150
gmaclennan
approved these changes
Mar 28, 2024
This was referenced Apr 11, 2024
This was referenced Jun 20, 2024
This was referenced Jul 25, 2024
This was referenced Aug 21, 2024
This was referenced Aug 29, 2024
This was referenced Sep 16, 2024
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.
Depends on #530.
If we use the "integer" JSON Schema type, we should save that as an INTEGER column, not a REAL column. Both will work for many numbers, but larger integers (like
2**63) can only be safely stored in INTEGERs. This should be a bit more reliable.As of this patch, we don't have any integer types in our schemas, so this has no effect. However, that may change as we address upcoming issues.