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

Support bigdecimal 0.4 #661

Open
Sytten opened this issue Jul 14, 2023 · 2 comments
Open

Support bigdecimal 0.4 #661

Sytten opened this issue Jul 14, 2023 · 2 comments

Comments

@Sytten
Copy link
Contributor

Sytten commented Jul 14, 2023

Motivation

Right now it's pinned to 0.3, but we can't force by default third party dependencies to use that version if they have looser requirements. So by default Diesel force example resolves to 0.4.1 which breaks the binder because traits are not matching. I think a >=0.3, <0.5 would be perfectly fine.

@joshburgess
Copy link

joshburgess commented Aug 6, 2024

This is causing problems in my production codebase at work while trying to update sqlx, because the latest version of sqlx is using bigdecimal 0.4. (Mixed codebase with plain sqlx usage and sea-query usage)

If I try to use bigdecimal 0.3, I'm missing trait implementations required by sqlx. If I try to use 0.4, I'm missing trait implementations required by sea-query.

@tyt2y3
Copy link
Member

tyt2y3 commented Aug 6, 2024

Upgrading sqlx to 0.8 is in the works. #798

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

No branches or pull requests

3 participants