Plume/migrations/sqlite/2018-05-13-122311_create_no.../up.sql

-- Your SQL goes here
CREATE TABLE notifications (
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    user_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL,
    creation_date DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    kind VARCHAR NOT NULL DEFAULT 'unknown',
    object_id INTEGER NOT NULL DEFAULT 0
)
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			`-- Your SQL goes here`
			`CREATE TABLE notifications (`
			`id INTEGER PRIMARY KEY AUTOINCREMENT,`
			`user_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL,`
align types between sqlite & postgres use DATETIME for SQLite's time type. This way, Diesel picks up on what it's supposed to be. 2018-09-16 14:22:18 +00:00			`creation_date DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,`
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			`kind VARCHAR NOT NULL DEFAULT 'unknown',`
			`object_id INTEGER NOT NULL DEFAULT 0`
			`)`