mirror of
https://github.com/isar/rusqlite.git
synced 2024-11-22 16:29:20 +08:00
commit
456c847bd6
@ -128,7 +128,7 @@ You can adjust this behavior in a number of ways:
|
||||
* If you use the `bundled`, `bundled-sqlcipher`, or `bundled-sqlcipher-vendored-openssl` features, `libsqlite3-sys` will use the
|
||||
[cc](https://crates.io/crates/cc) crate to compile SQLite or SQLCipher from source and
|
||||
link against that. This source is embedded in the `libsqlite3-sys` crate and
|
||||
is currently SQLite 3.36.0 (as of `rusqlite` 0.26.0 / `libsqlite3-sys`
|
||||
is currently SQLite 3.37.0 (as of `rusqlite` 0.26.0 / `libsqlite3-sys`
|
||||
0.23.0). This is probably the simplest solution to any build problems. You can enable this by adding the following in your `Cargo.toml` file:
|
||||
```toml
|
||||
[dependencies.rusqlite]
|
||||
|
@ -354,8 +354,6 @@ impl Connection {
|
||||
|
||||
/// Register a callback function to be invoked whenever
|
||||
/// a transaction is committed.
|
||||
///
|
||||
/// The callback returns `true` to rollback.
|
||||
#[inline]
|
||||
pub fn rollback_hook<F>(&self, hook: Option<F>)
|
||||
where
|
||||
|
Loading…
Reference in New Issue
Block a user