-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Faillible Queryable #2599
Faillible Queryable #2599
Conversation
One approach to fixing diesel-rs#2523
As with #2559 I would like to see a complete port of the repo before deciding anything else here. Generally speaking I think that one may be a better solution than the other PR, but I'm not entirely sure yet. |
I beleive that's it :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After reviewing both PR's I find that one the better solution. With the suggested change we could even make that not-breaking for downstream code with a minimal maintenance burden on our side.
I still would like to get a benchmark run on this (seems like the CI was not fixed with the last commit, I will push a new fix to master.).
That's also what I thought after experimenting with the other one. 🙂 |
Fork dropped, we're finally back to following diesel master, woohoo! 😊 |
Fixes #2523
TODO:
#[diesel(deserialize_as)]
at top-level when derivingQueryable
(as described at No way to express inconsistency when deserializing forQueryable
data since #2182 #2523 (comment))