Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs claim that u64 is a valid SQLite Encode/Decode type but it is then unimplemented. #1374

Closed
HamishWHC opened this issue Aug 13, 2021 · 2 comments · Fixed by #1965
Closed

Comments

@HamishWHC
Copy link

u64 is present here, but not implemented here or here.

@xamgore
Copy link

xamgore commented Dec 23, 2021

Seems that @dignifiedquire has decided not to implement it yet.

@v1bri
Copy link

v1bri commented Jan 12, 2022

To summarize that issue thread, SQLite uses only signed integers which have no lossless conversion from u64. Since the sqlx::Encode trait has no way to signal a conversion error, support for u64 is being deferred pending such a change to the trait. Perhaps this can be turned into a feature request (ex: for sqlx::TryEncode or similar).

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 a pull request may close this issue.

3 participants