An awesome SurrealDB migration tool, with a user-friendly CLI and a versatile Rust library that enables seamless integration into any project.
Warning This project is not production-ready, use at your own risk.
This project can be used:
cargo add surrealdb-migrations
cargo install surrealdb-migrations
The SurrealDB Migrations project aims to simplify the creation of a SurrealDB database schema and the evolution of the database through migrations. A typical SurrealDB migration project is divided into 3 categories: schema, event and migration.
A schema file represents no more than one SurrealDB table. The list of schemas can be seen as the Query model (in a CQRS pattern). The schemas
folder can be seen as a view of the current data model.
An event file represents no more than one SurrealDB event and the underlying table. The list of events can be seen as the Command model (in a CQRS pattern). The events
folder can be seen as a view of the different ways to update the data model.
A migration file represents a change in SurrealDB data. It can be a change in the point of time between two schema changes. Examples are: when a column is renamed or dropped, when a table is renamed or dropped, when a new data is required (with default value), etc...
You can start a migration project by scaffolding a new project using the following command line:
surrealdb-migrations scaffold empty
This will create the necessary folders and files in order to perform migrations. The empty
template should look like this:
There are a number of pre-defined templates so you can play around and get started quickly.
Once you have created your migration project, you can start writing your own model. Based on the folders you saw earlier, you can create schema files, event files and migration files.
You can create strict schema files that represent tables stored in SurrealDB.
surrealdb-migrations create schema post --fields title,content,author,created_at,status
This will create a schemaless table with predefined fields:
```surql DEFINE TABLE post SCHEMALESS;
DEFINE FIELD title ON post; DEFINE FIELD content ON post; DEFINE FIELD author ON post; DEFINE FIELD created_at ON post; DEFINE FIELD status ON post; ```
You can also create events in the same way.
surrealdb-migrations create event publish_post --fields post_id,created_at
This will define a table event with predefined fields:
```surql DEFINE TABLE publish_post SCHEMALESS;
DEFINE FIELD postid ON publishpost; DEFINE FIELD createdat ON publishpost;
DEFINE EVENT publishpost ON TABLE publishpost WHEN $before == NONE THEN ( # TODO ); ```
And when updating data, you can create migration files this way:
surrealdb-migrations create AddAdminUser
This will create a new file using the current date & time of the day, like 20230317_153201_AddAdminUser.surql
for example. All migrations files should be listed in a temporal order.
Finally, when you are ready, you can apply your schema and migrations to the database using the following command line:
surrealdb-migrations apply
Or directly inside your Rust project using the following code:
```rust use surrealdb_migrations::{SurrealdbConfiguration, SurrealdbMigrations};
async fn main() { let db_configuration = SurrealdbConfiguration::default();
SurrealdbMigrations::new(db_configuration)
.up()
.await
.expect("Failed to apply migrations");
} ```
Repeat the process from step 2. Change schema and/or create data change migrations.
To help you get started quickly, there is a list of predefined templates you can use:
empty
- The smallest migration project you can create, a clean schema with an already defined script_migration
table to store the applied migrationsblog
- A blog domain model, with users having the ability to publish/unpublish posts and commentsecommerce
- An ecommerce domain model, with customers having the ability to purchase productsYou can scaffold a project using any of these templates using the following command line:
surrealdb-migrations scaffold <TEMPLATE>
You can create a .surrealdb
configuration file at the root of your project. This way you won't have to set the same configuration values every time.
```toml [core] path = "./tests-files"
[db] url = "localhost:8000" username = "root" password = "root" ns = "test" db = "test" ```
In the core
section, you can define the path to your schema/migration files, if it is not the current folder.
In the db
section, you can define the values used to access your SurrealDB database. It can be the url
, username
, password
, the namespace ns
or the name of the database db
.