commit | ab6dd953f72bc1ca259f96aaddb081a025a96595 | [log] [tgz] |
---|---|---|
author | Sean Griffin <sean@seantheprogrammer.com> | Thu Aug 02 14:40:10 2018 -0600 |
committer | Sean Griffin <sean@seantheprogrammer.com> | Thu Aug 02 14:40:10 2018 -0600 |
tree | b3b2000d9a593fba7c0b1d2ab912bcdeb95180e7 | |
parent | 20501ece0514b5bc01ec12356158081f854b4213 [diff] |
Allow `now` to coerce to `Nullable<Timestamp>` It is able to coerce to `Nullable<Timestamptz>`, so it makes no sense for it not to coerce to `Nullable<Timestamp>`. I'd love to use `expression::Nullable<now>` both in the test and as the return type of the coercion (or remove the nullable coercion entirely). However, `expression::Nullable` can only be used in select clauses with left outer joins for complicated coherence reasons
API Documentation: latest release – master branch
Diesel gets rid of the boilerplate for database interaction and eliminates runtime errors without sacrificing performance. It takes full advantage of Rust's type system to create a low overhead query builder that “feels like Rust.”
Find our extensive Getting Started tutorial at https://diesel.rs/guides/getting-started. Guides on more specific features are coming soon.
If you run into problems, Diesel has a very active Gitter room. You can come ask for help at gitter.im/diesel-rs/diesel
Anyone who interacts with Diesel in any space, including but not limited to this GitHub repository, must follow our code of conduct.
Licensed under either of these:
Unless you explicitly state otherwise, any contribution you intentionally submit for inclusion in the work, as defined in the Apache-2.0 license, shall be dual-licensed as above, without any additional terms or conditions.