reviews

Reviews are the m:n mapping table between books and shelves. This means books that are just on your to-read shelf still have a review, connecting the book with your shelf. I don't make the rules.

1 row where book_id = 41018921

View and edit SQL

Suggested facets: date_added (date), date_updated (date), read_at (date)

id ▼ book_id user_id rating text date_added date_updated read_at started_at
2984077010 Ars Longa, Vita Brevis 41018921 rixx 41972609 2 [Ars Longa, Vita Brevis](<a target="_blank" href="https://slatestarcodex.com/2017/11/09/ars-longa-vita-brevis/" rel="nofollow">https://slatestarcodex.com/2017/11/09...</a>) is not one of *Scott Alexander*'s best stories. Skippable, to me, because the content lost out against the style. (What is it with rationalist fiction and that stilted style? Can't people make an argument without sounding like badly written robot hybrids?) 2019-09-20T06:03:26-07:00 2020-02-23T11:17:01-08:00 2019-09-20  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE [reviews] (
   [id] TEXT PRIMARY KEY,
   [book_id] TEXT REFERENCES [books]([id]),
   [user_id] TEXT REFERENCES [users]([id]),
   [rating] TEXT,
   [text] TEXT,
   [date_added] TEXT,
   [date_updated] TEXT
, [read_at] TEXT, [started_at] TEXT);
Powered by Datasette · Query took 84.34ms