commit | 3ae353c3aff8a7ea64ed6cb39b3a045ac86cd60e | [log] [tgz] |
---|---|---|
author | Sean Griffin <sean@seantheprogrammer.com> | Thu Aug 24 14:13:56 2017 -0400 |
committer | Sean Griffin <sean@seantheprogrammer.com> | Thu Aug 24 14:20:55 2017 -0400 |
tree | 20fda60321d7234b7abdd23e945b2291cb0489a6 | |
parent | ff84e5398cbe508fc1e5a52029ca2ff8ce9e25ca [diff] |
Release v0.16.0 This release contains some changes to how joins work with Diesel, which we wanted to release as far in advance of 1.0 as possible. With this release, `#[belongs_to]` no longer generates the code required to join between two tables. The macro `joinable!` must be invoked instead. However, if you are using `infer_schema!` or `diesel print-schema`, these invocations will be generated based on the foreign keys in your database. Also included in this release is the ability to rename columns. This is most useful when your columns conflict with Rust keywords. See the changelog for details. In addition to the Diesel core team, 11 people contributed to this release. A huge thank you to: - Alex Alvarez dominalexican@gmail.com - Georg Semmler georg_semmler_05@web.de - Graham Grochowski ggrochow@gmail.com - JD Gonzales jd_gonzales@icloud.com - Lance Carlson lancecarlson@gmail.com - Maciej fiedzia@gmail.com - Robert Balicki robert.balicki@gmail.com - Sharad Chand sharad.d.chand@gmail.com - Taryn Hill taryn@phrohdoh.com - debris marek.kotewicz@gmail.com - klieth klieth@users.noreply.github.com
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”.
You can find an extensive Getting Started tutorial at http://diesel.rs/guides/getting-started. Guides on more specific features will be coming soon.
Anyone who interacts with Diesel in any space including but not limited to this GitHub repository is expected to follow our code of conduct
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.