Rusqlite Migration is a simple and performant schema migration library for rusqlite.
- Performance:
- Fast database opening: to keep track of the current migration state, most tools create one or more tables in the database. These tables require parsing by SQLite and are queried with SQL statements. This library uses the
user_versionvalue instead. It’s much lighter as it is just an integer at a fixed offset in the SQLite file. - Fast compilation: this crate is very small and does not use macros to define the migrations.
- Fast database opening: to keep track of the current migration state, most tools create one or more tables in the database. These tables require parsing by SQLite and are queried with SQL statements. This library uses the
- Simplicity: this crate strives for simplicity. Just define a set of SQL statements as strings in your Rust code. Add more SQL statements over time as needed. No external CLI required. Additionally, rusqlite_migration works especially well with other small libraries complementing rusqlite, like serde_rusqlite.
Here, we define SQL statements to run with Migrations::new() and run these (if necessary) with Migrations::to_latest().
use rusqlite::{params, Connection};
use rusqlite_migration::{Migrations, M};
// 1️⃣ Define migrations
let migrations = Migrations::new(vec![
M::up("CREATE TABLE friend(name TEXT NOT NULL);"),
// In the future, add more migrations here:
//M::up("ALTER TABLE friend ADD COLUMN email TEXT;"),
]);
let mut conn = Connection::open_in_memory().unwrap();
// Apply some PRAGMA, often better to do it outside of migrations
conn.pragma_update_and_check(None, "journal_mode", &"WAL", |_| Ok(())).unwrap();
// 2️⃣ Update the database schema, atomically
migrations.to_latest(&mut conn).unwrap();
// 3️⃣ Use the database 🥳
conn.execute("INSERT INTO friend (name) VALUES (?1)", params!["John"])
.unwrap();Please see the examples folder for more, in particular:
asyncmigrations in thequick_start_async.rsfile- migrations with multiple SQL statements (using for instance
r#"…"orinclude_str!(…)) - migrations defined from a directory with SQL files
- use of lazy_static
- migrations to previous versions (downward migrations)
I’ve also made a cheatsheet of SQLite pragma for improved performance and consistency.
To test that the migrations are working, you can add this in your test module:
#[test]
fn migrations_test() {
assert!(MIGRATIONS.validate().is_ok());
}The migrations object is also suitable for serialisation with insta, using the Debug serialisation. You can store a snapshot of your migrations like this:
#[test]
fn migrations_insta_snapshot() {
let migrations = Migrations::new(vec![
// ...
]);
insta::assert_debug_snapshot!(migrations);
}Rusqlite_migration provides several Cargo features. They are:
from-directory: enable loading migrations from *.sql files in a given directoryalpha-async-tokio-rusqlite: enable support for async migrations withtokio-rusqlite. As the name implies, there are no API stability guarantees on this feature.
This crate is actively used in a number of projects. You can find up-to-date list of those on:
A number of contributors are also reporting issues as they arise, another indicator of active use.
Contributions (documentation or code improvements in particular) are welcome, see contributing!
We use various tools for testing that you may find helpful to install locally (e.g. to fix failing CI checks):
I would like to thank all the contributors, as well as the authors of the dependencies this crate uses.
Thanks to Migadu for offering a discounted service to support this project. It is not an endorsement by Migadu though.
![dependabot-preview[bot] avatar](https://avatars.githubusercontent.com/in/2141?v=4 "dependabot-preview[bot]")
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent