Mark u64 as unsupported on SQLite in column-types table - #181
Merged
Conversation
|
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
1 participant
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.
The column-types table listed
u64→ SQLiteinteger, implying it works. It doesn't: SQLite stores only 64-bit signed integers, and thesqlxSQLite driver does not encodeu64(values abovei64::MAXcan't be represented).u8/u16/u32are fine — they fit in signed 64-bit — so only theu64row is wrong.Changed the SQLite cell to
unsupported¹and added a footnote pointing at the workaround (i64, orString/Vec<u8>) and the long-standing tracking issue. Applied to both the English doc and the zh-CN mirror.Context: SeaQL/sea-orm#3150 (rediscovered) → duplicate of SeaQL/sea-orm#1400 (2023). A docs fix for this was attempted back then (#88) but never made it in.