Plume/migrations/sqlite/2018-12-17-221135_comment_visibility/up.sql

-- Your SQL goes here
ALTER TABLE comments ADD public_visibility BOOLEAN NOT NULL DEFAULT 't';

CREATE TABLE comment_seers (
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    comment_id INTEGER REFERENCES comments(id) ON DELETE CASCADE NOT NULL,
    user_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL,
    UNIQUE (comment_id, user_id)
)
Comment visibility (#364) Add some support for comment visibility, fix #217 This add a new column to comment, denoting if they are public or not, and a new table linking private comments to those allowed to read them. There is currently no way to write a private comment from Plume. Git is having a hard time what happened in Comment::from_activity, but most of it is just re-indentation because a new block was needed to please the borrow checker. I've marked with comments where things actually changed. At this point only mentioned users can see private comments, even when posted as "follower only" or equivalent. What should we do when someone isn't allowed to see a comment? Hide the whole thread, or just the comment? If hiding just the comment, should we mark there is a comment one can't see, but answers they can, or put other comments like if they answered to the same comment the hidden one do? 2018-12-24 10:23:04 +00:00			`-- Your SQL goes here`
			`ALTER TABLE comments ADD public_visibility BOOLEAN NOT NULL DEFAULT 't';`

			`CREATE TABLE comment_seers (`
			`id INTEGER PRIMARY KEY AUTOINCREMENT,`
			`comment_id INTEGER REFERENCES comments(id) ON DELETE CASCADE NOT NULL,`
			`user_id INTEGER REFERENCES users(id) ON DELETE CASCADE NOT NULL,`
			`UNIQUE (comment_id, user_id)`
			`)`