commit | 0d106bcb95c48fb4ceb1c3fe413cc2add1bb8ec9 | [log] [tgz] |
---|---|---|
author | Georg Semmler <github@weiznich.de> | Thu Jan 13 10:23:05 2022 +0100 |
committer | Georg Semmler <github@weiznich.de> | Thu Jan 13 10:23:05 2022 +0100 |
tree | a7c6b7c2de851fd1c6815782df020b54ca1bbf69 | |
parent | 09f8bcd78e3fb634ed69c66f46695b821a5b3822 [diff] |
Fix #3016 This demonstrate a potential fix for #3016 by using the async libpq interface + busy polling. This allows us to abort polling as soon as we reach the timeout. I see multiple issues with this approach: * Add's new methods to `Connection` (`get_timeout`/`set_timeout`). This could likely be avoided by exposing them directly on `PgConnection`. On the other hand that would, at least for 1.4.x imply that we cannot use those timeout only for the `is_valid` function. It would be all or nothing then. * This uses busy polling, which could be quite inefficient. I'm not sure what better posibilities there are without pulling in tokio/mio/async_std.
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. For help with longer questions and discussion about the future of Diesel, visit our discourse forum.
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.