nyanoblog/migrations/20221211175753_create_likes.sql

CREATE TABLE likes (
    iri VARCHAR,
    note_id BIGINT REFERENCES notes (id) ON DELETE CASCADE,
    account_id BIGINT REFERENCES accounts (id) ON DELETE CASCADE,
    created_at TIMESTAMP NOT NULL DEFAULT now(),
    CONSTRAINT likes_pkey PRIMARY KEY (note_id, account_id)
);

CREATE UNIQUE INDEX index_likes_on_iri ON likes (iri);
add likes 2022-12-11 20:44:06 +01:00			`CREATE TABLE likes (`
add iri column 2022-12-25 15:57:33 +01:00			`iri VARCHAR,`
add likes 2022-12-11 20:44:06 +01:00			`note_id BIGINT REFERENCES notes (id) ON DELETE CASCADE,`
			`account_id BIGINT REFERENCES accounts (id) ON DELETE CASCADE,`
refactor model IDs to use safe types This is a major refactor that introduces a new generic type Id<T, I> for tagging any ID with the model they reference without any runtime overhead. From now on, it should be pretty much impossible to pass e.g. a note ID to a function that expects, say, an account ID. Furthermore, the follow and like tables have been simplified to use the two IDs that define the relationship as a composite primary key. Finally, likes now have a memory cache. 2023-01-20 16:45:12 +01:00			`created_at TIMESTAMP NOT NULL DEFAULT now(),`
			`CONSTRAINT likes_pkey PRIMARY KEY (note_id, account_id)`
add likes 2022-12-11 20:44:06 +01:00			`);`

add iri column 2022-12-25 15:57:33 +01:00			`CREATE UNIQUE INDEX index_likes_on_iri ON likes (iri);`