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

Figure out how to allow querying values against a nullable column #4

Closed
sgrif opened this issue Oct 7, 2015 · 0 comments
Closed

Figure out how to allow querying values against a nullable column #4

sgrif opened this issue Oct 7, 2015 · 0 comments

Comments

@sgrif
Copy link
Member

sgrif commented Oct 7, 2015

I'm debating whether or not to have foo.eq(None) result in foo IS NULL or not. Either way, for ergonomics, we should allow foo.eq("bar") in addition to foo.eq(Some("bar")). At the moment, attempting to write this ToSql implementation results in overlap both with the impl for Option<T>, and for &'a T. I think we need specialization for this to work.

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

1 participant