Skip to content
Tauri
Releases

SQL

Plugin providing an interface for the frontend to communicate with SQL databases through sqlx. It supports the SQLite, MySQL and PostgreSQL drivers, enabled by a Cargo feature.

Install

This plugin requires a Rust version of at least 1.75

Firstly, you have to install Core plugin by adding the following to your Cargo.toml file:

src-tauri/Cargo.toml
[dependencies.tauri-plugin-sql]
features = ["sqlite"] # or "postgres", or "mysql"
version = "2.0.0-beta"

Then, you have to add JavaScript Guest bindings using your preferred JavaScript package manager.

npm add @tauri-apps/plugin-sql

Usage

First you need to register the core plugin with Tauri:

src-tauri/src/main.rs
fn main() {
tauri::Builder::default()
.plugin(tauri_plugin_sql::Builder::default().build())
.run(tauri::generate_context!())
.expect("error while running tauri application");
}

Afterwards all the plugin’s APIs are available through the JavaScript guest bindings:

The path is relative to tauri::api::path::BaseDirectory::App

import Database from '@tauri-apps/plugin-sql';
const db = await Database.load('sqlite:test.db');
await db.execute('INSERT INTO ...');

Syntax

We use sqlx as the underlying library and adopt their query syntax.

Use the ”$#” syntax when substituting query data

const result = await db.execute(
"INSERT into todos (id, title, status) VALUES ($1, $2, $3)",
[todos.id, todos.title, todos.status],
);
const result = await db.execute(
"UPDATE todos SET title = $1, status = $2 WHERE id = $3",
[todos.title, todos.status, todos.id],
);

Migrations

This plugin supports database migrations, allowing you to manage database schema evolution over time.

Defining Migrations

Migrations are defined in Rust using the Migration struct. Each migration should include a unique version number, a description, the SQL to be executed, and the type of migration (Up or Down).

Example of a migration:

use tauri_plugin_sql::{Migration, MigrationKind};
let migration = Migration {
version: 1,
description: "create_initial_tables",
sql: "CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT);",
kind: MigrationKind::Up,
};

Adding Migrations to the Plugin Builder

Migrations are registered with the Builder struct provided by the plugin. Use the add_migrations method to add your migrations to the plugin for a specific database connection.

Example of adding migrations:

src-tauri/src/main.rs
use tauri_plugin_sql::{Builder, Migration, MigrationKind};
fn main() {
let migrations = vec![
// Define your migrations here
Migration {
version: 1,
description: "create_initial_tables",
sql: "CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT);",
kind: MigrationKind::Up,
}
];
tauri::Builder::default()
.plugin(
tauri_plugin_sql::Builder::default()
.add_migrations("sqlite:mydatabase.db", migrations)
.build(),
)
...
}

Applying Migrations

Migrations are applied automatically when the plugin is initialized. The plugin runs these migrations against the database specified by the connection string. Ensure that the migrations are defined in the correct order and are idempotent (safe to run multiple times).

Migration Management

  • Version Control: Each migration must have a unique version number. This is crucial for ensuring the migrations are applied in the correct order.
  • Idempotency: Write migrations in a way that they can be safely re-run without causing errors or unintended consequences.
  • Testing: Thoroughly test migrations to ensure they work as expected and do not compromise the integrity of your database.

Permissions

By default all plugin commands are blocked and cannot be accessed. You must define a list of permissions in your capabilities configuration.

See Access Control List for more information.

src-tauri/capabilities/main.json
{
"$schema": "../gen/schemas/desktop-schema.json",
"identifier": "main-capability",
"description": "Capability for the main window",
"windows": ["main"],
"permissions": [
"sql:allow-load",
"sql:allow-execute",
]
}
PermissionDescription
sql:allow-closeEnables the close command without any pre-configured scope.
sql:deny-closeDenies the close command without any pre-configured scope.
sql:allow-executeEnables the execute command without any pre-configured scope.
sql:deny-executeDenies the execute command without any pre-configured scope.
sql:allow-loadEnables the load command without any pre-configured scope.
sql:deny-loadDenies the load command without any pre-configured scope.
sql:allow-selectEnables the select command without any pre-configured scope.
sql:deny-selectDenies the select command without any pre-configured scope.

© 2024 Tauri Contributors. CC-BY / MIT