Crates.io | sqlx_migrator |
lib.rs | sqlx_migrator |
version | 0.16.1 |
source | src |
created_at | 2022-05-28 07:14:33.421702 |
updated_at | 2024-10-25 07:43:23.328208 |
description | Migrator for writing sqlx migration using Rust instead of SQL |
homepage | https://github.com/iamsauravsharma/sqlx_migrator |
repository | https://github.com/iamsauravsharma/sqlx_migrator |
max_upload_size | |
id | 595624 |
size | 201,411 |
A Rust library for writing SQLX migrations using Rust instead of SQL.
License | Crates Version | Docs |
---|---|---|
Supported Databases:
Add sqlx_migrator
to your Cargo.toml
with the appropriate database feature:
sqlx_migrator = { version = "0.16.1", features=["postgres"] }
OR
sqlx_migrator = { version = "0.16.1", features=["mysql"] }
OR
sqlx_migrator = { version = "0.16.1", features=["sqlite"] }
OR
sqlx_migrator = { version = "0.16.1", features=[
"any",
# Plus any one of above database driver
] }
To use sqlx_migrator
, implement the Operation
trait to define your migration logic. Here's an example using PostgreSQL:
use sqlx_migrator::error::Error;
use sqlx_migrator::operation::Operation;
pub(crate) struct FirstOperation;
#[async_trait::async_trait]
impl Operation<sqlx::Postgres> for FirstOperation {
// Up function runs apply migration
async fn up(&self, connection: &mut sqlx::PgConnection) -> Result<(), Error> {
sqlx::query("CREATE TABLE sample (id INTEGER PRIMARY KEY, name TEXT)")
.execute(connection)
.await?;
Ok(())
}
// down migration runs down migration
async fn down(connection: &mut sqlx::PgConnection) -> Result<(), Error> {
sqlx::query("DROP TABLE sample").execute(connection).await?;
Ok(())
}
}
After defining your operations, you can create a migration:
use sqlx_migrator::error::Error;
use sqlx_migrator::migration::Migration;
use sqlx_migrator::operation::Operation;
pub(crate) struct FirstMigration;
impl Migration<sqlx::Postgres> for FirstMigration {
// app where migration lies can be any value
fn app(&self) -> &str {
"main"
}
// name of migration
// Combination of migration app and name must be unique to work properly expects for virtual migration
fn name(&self) -> &str {
"first_migration"
}
// Use the parent function to add parents of a migration.
// If you cannot access or create the parent migration easily, you can also use
// `(A,N) where A: AsRef<str>, N: AsRef<str>` where A is the app name
// and N is the name of the migration.
fn parents(&self) -> Vec<Box<dyn Migration<sqlx::Postgres>>> {
vec![]
// vec![("main", "initial_migration"), AnotherInitialMigration]
}
// use operations function to add operation part of migration
fn operations(&self) -> Vec<Box<dyn Operation<sqlx::Postgres>>> {
vec![Box::new(FirstOperation)]
}
// Migration trait also have multiple other function see docs for usage
}
This migration can be represented in a simpler form using macros:
use sqlx_migrator::vec_box;
sqlx_migrator::migration!(
sqlx::Postgres,
FirstMigration,
"main",
"first_migration",
vec_box![],
vec_box![FirstOperation]
);
// OR
sqlx_migrator::postgres_migration!(
FirstMigration,
"main",
"first_migration",
vec_box![],
vec_box![FirstOperation]
);
If your up and down queries are simple strings, you can simplify the implementation:
sqlx_migrator::postgres_migration!(
FirstMigration,
"main",
"first_migration",
sqlx_migrator::vec_box![],
sqlx_migrator::vec_box![
(
"CREATE TABLE sample (id INTEGER PRIMARY KEY, name TEXT)",
"DROP TABLE sample"
)
]
);
Finally, create a migrator to run your migrations:
use sqlx_migrator::migrator::{Info, Migrate, Migrator};
use sqlx::Postgres;
#[tokio::main]
async fn main() {
let uri = std::env::var("DATABASE_URL").unwrap();
let pool = sqlx::Pool::<Postgres>::connect(&uri).await.unwrap();
let mut migrator = Migrator::default();
migrator.add_migration(Box::new(FirstMigration));
}
You can run migrations directly or integrate them into a CLI:
use sqlx_migrator::migrator::Plan;
let mut conn = pool.acquire().await?;
// use apply all to apply all pending migration
migrator.run(&mut *conn, Plan::apply_all()).await.unwrap();
// or use revert all to revert all applied migrations
migrator.run(&mut *conn, Plan::revert_all()).await.unwrap();
use sqlx_migrator::cli::MigrationCommand;
MigrationCommand::parse_and_run(&mut *conn, Box::new(migrator)).await.unwrap();
Or extend your own CLI with migrator support:
#[derive(clap::Parser)]
struct Cli {
#[command(subcommand)]
sub_command: CliSubcommand
}
#[derive(clap::Subcommand)]
enum CliSubcommand {
#[command()]
Migrator(sqlx_migrator::cli::MigrationCommand)
}
impl Cli {
async fn run() {
let cli = Self::parse();
// create connection
match cli.sub_command {
Migrator(m) => {
m.run(&mut conn, Box::new(migrator)).await.unwrap()
}
}
}
}
To migrate from sqlx sql based migration you have two alternative:
<COMMAND_NAME> apply --fake
: Follow the usage example above.use sqlx_migrator::error::Error;
use sqlx_migrator::operation::Operation;
pub(crate) struct SqlxOperation;
#[async_trait::async_trait]
impl Operation<sqlx::Postgres> for SqlxOperation {
async fn up(&self, connection: &mut sqlx::PgConnection) -> Result<(), Error> {
sqlx::migrate!("migrations").run(connection).await?;
Ok(())
}
async fn down(&self, connection: &mut sqlx::PgConnection) -> Result<(), Error> {
sqlx::migrate!("migrations").undo(connection, 0).await?;
Ok(())
}
}