Plume/migrations/sqlite/2018-09-02-111458_create_me.../up.sql

-- Your SQL goes here
CREATE TABLE medias (
    id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
    file_path TEXT NOT NULL DEFAULT '',
    alt_text TEXT NOT NULL DEFAULT '',
    is_remote BOOLEAN NOT NULL DEFAULT 'f',
    remote_url TEXT,
    sensitive BOOLEAN NOT NULL DEFAULT 'f',
    content_warning TEXT,
    owner_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL
)
Add a Media model 2018-09-02 11:34:48 +00:00			`-- Your SQL goes here`
			`CREATE TABLE medias (`
align types between sqlite & postgres this one's achieved by adding "NOT NULL" at the correct position in SQLite's create tables. 2018-09-17 09:08:58 +00:00			`id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,`
Add a Media model 2018-09-02 11:34:48 +00:00			`file_path TEXT NOT NULL DEFAULT '',`
			`alt_text TEXT NOT NULL DEFAULT '',`
			`is_remote BOOLEAN NOT NULL DEFAULT 'f',`
			`remote_url TEXT,`
			`sensitive BOOLEAN NOT NULL DEFAULT 'f',`
add sqlite migrations we move our PostgreSQL specific migrations to a subdirectory. The SQLite migrations have been created by running `diesel` against a copy, and then fixing what's broken. In the end i reduced all modifications to a single create, since we are starting out fresh with SQLite. n.b.: i'm not entirely happy with the results yet, because diesel heavily modifies our `plume-models/src/schema.rs`. I'll keep fiddling until we have the same types between the two databases. 2018-09-15 11:38:09 +00:00			`content_warning TEXT,`
			`owner_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL`
Add a Media model 2018-09-02 11:34:48 +00:00			`)`