Plume/migrations/sqlite/2018-05-10-154336_create_likes/up.sql

-- Your SQL goes here
CREATE TABLE likes (
    id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
    user_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL,
    post_id INTEGER REFERENCES posts(id) ON DELETE CASCADE NOT NULL,
    ap_url VARCHAR NOT NULL default '',
    creation_date DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP
)
Add a model for likes 2018-05-10 15:54:35 +00:00			`-- Your SQL goes here`
			`CREATE TABLE likes (`
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 model for likes 2018-05-10 15:54:35 +00:00			`user_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL,`
			`post_id INTEGER REFERENCES posts(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			`ap_url VARCHAR NOT NULL default '',`
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 a model for likes 2018-05-10 15:54:35 +00:00			`)`