Rusqlcipher is an ergonomic wrapper for using SQLCipher from Rust. It attempts to expose an interface similar to rust-postgres. View the full API documentation.
extern crate rusqlcipher;
extern crate time;
use time::Timespec;
use rusqlcipher::Connection;
#[derive(Debug)]
struct Person {
id: i32,
name: String,
time_created: Timespec,
data: Option<Vec<u8>>
}
fn main() {
let conn = Connection::open_in_memory().unwrap();
conn.execute("CREATE TABLE person (
id INTEGER PRIMARY KEY,
name TEXT NOT NULL,
time_created TEXT NOT NULL,
data BLOB
)", &[]).unwrap();
let me = Person {
id: 0,
name: "Steven".to_string(),
time_created: time::get_time(),
data: None
};
conn.execute("INSERT INTO person (name, time_created, data)
VALUES (?1, ?2, ?3)",
&[&me.name, &me.time_created, &me.data]).unwrap();
let mut stmt = conn.prepare("SELECT id, name, time_created, data FROM person").unwrap();
let person_iter = stmt.query_map(&[], |row| {
Person {
id: row.get(0),
name: row.get(1),
time_created: row.get(2),
data: row.get(3)
}
}).unwrap();
for person in person_iter {
println!("Found person {:?}", person.unwrap());
}
}
This work is based on rusqlite
and SQLCipher
.
This package has precompiled SQLCipher to use OpenSSL 1.1.0 or newer and replaces the following three files in libsqlcipher-sys/sqlite3/: sqlite3.c, sqlite3.h, sqlite3ext.h. See openssl-sys
for information on compiling openssl. SQLCipher has been modified to use HMAC-SHA256 instead of the default HMAC-SHA1.
The base rusqlcipher
package supports SQLite version 3.6.8 or newer. If you need
support for older versions, please file an issue. Some cargo features require a
newer SQLite version; see details below.
Rusqlite provides several features that are behind Cargo features. They are:
load_extension
allows loading dynamic library-based SQLite3 extensions.backup
allows use of SQLite's online backup API. Note: This feature requires SQLite 3.6.11 or later.functions
allows you to load Rust closures into SQLite connections for use in queries. Note: This feature requires SQLite 3.7.3 or later.trace
allows hooks into SQLite's tracing and profiling APIs. Note: This feature requires SQLite 3.6.23 or later.blob
givesstd::io::{Read, Write, Seek}
access to SQL BLOBs. Note: This feature requires SQLite 3.7.4 or later.limits
allows you to set and retrieve SQLite's per connection limits.chrono
implementsFromSql
andToSql
for various types from thechrono
crate.serde_json
implementsFromSql
andToSql
for theValue
type from theserde_json
crate.bundled
uses a bundled version of sqlite3. This is a good option for cases where linking to sqlite3 is complicated, such as Windows.sqlcipher
looks for the SQLCipher library to link against instead of SQLite. This feature is mutually exclusive withbundled
.
libsqlcipher-sys
is a separate crate from rusqlcipher
that provides the Rust
declarations for SQLite's C API. By default, libsqlcipher-sys
attempts to find a SQLite library that already exists on your system using pkg-config, or a
Vcpkg installation for MSVC ABI builds.
rusqlcipher
also depends on OpenSSL version 1.1.0 or above.
You can adjust this behavior in a number of ways:
- If you use the
bundled
feature,libsqlcipher-sys
will use the gcc crate to compile SQLite from source and link against that. This source is embedded in thelibsqlcipher-sys
crate and is currently SQLite 3.15.2 (as ofrusqlcipher
0.10.1 /libsqlcipher-sys
0.7.1). This is probably the simplest solution to any build problems. You can enable this by adding the following in yourCargo.toml
file:[dependencies.rusqlcipher] version = "0.11.0" features = ["bundled"]
- You can set the
SQLITE3_LIB_DIR
to point to directory containing the SQLite library. - Installing the sqlite3 development packages will usually be all that is required, but
the build helpers for pkg-config
and vcpkg have some additional configuration
options. The default when using vcpkg is to dynamically link.
vcpkg install sqlite3:x64-windows
will install the required library.
We use bindgen to generate the Rust
declarations from SQLite's C header file. bindgen
recommends
running this as part of the build process of libraries that used this. We tried
this briefly (rusqlcipher
0.10.0, specifically), but it had some annoyances:
- The build time for
libsqlcipher-sys
(and thereforerusqlcipher
) increased dramatically. - Running
bindgen
requires a relatively-recent version of Clang, which many systems do not have installed by default. - Running
bindgen
also requires the SQLite header file to be present.
As of rusqlcipher
0.1.0, we avoid running bindgen
at build-time by shipping
pregenerated bindings for several versions of SQLite. When compiling
rusqlcipher
, we use your selected Cargo features to pick the bindings for the
minimum SQLite version that supports your chosen features. If you are using
libsqlcipher-sys
directly, you can use the same features to choose which
pregenerated bindings are chosen:
min_sqlite_version_3_6_8
- SQLite 3.6.8 bindings (this is the default)min_sqlite_version_3_6_11
- SQLite 3.6.11 bindingsmin_sqlite_version_3_6_23
- SQLite 3.6.23 bindingsmin_sqlite_version_3_7_3
- SQLite 3.7.3 bindingsmin_sqlite_version_3_7_4
- SQLite 3.7.4 bindings
If you use the bundled
feature, you will get pregenerated bindings for the
bundled version of SQLite. If you need other specific pregenerated binding
versions, please file an issue. If you want to run bindgen
at buildtime to
produce your own bindings, use the buildtime_bindgen
Cargo feature.
Michael Lodder, redmike7@gmail.com
John Gallagher, johnkgallagher@gmail.com
Rusqlcipher is available under the Apache Version 2 license. See the LICENSE file for more info. Rusqlite is available under the MIT license. See the ORIGLICENSE file for more info.