Plume/migrations/sqlite/2018-05-01-124607_create_fo.../up.sql

-- Your SQL goes here
CREATE TABLE follows (
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    follower_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL,
    following_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL,
    ap_url TEXT NOT NULL default ''
)
Add a follow model 2018-05-01 13:06:31 +00:00			`-- Your SQL goes here`
			`CREATE TABLE follows (`
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			`id INTEGER PRIMARY KEY AUTOINCREMENT,`
Add a follow model 2018-05-01 13:06:31 +00:00			`follower_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL,`
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			`following_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL,`
			`ap_url TEXT NOT NULL default ''`
Add a follow model 2018-05-01 13:06:31 +00:00			`)`