issue_comments
3 rows where author_association = "OWNER", "created_at" is on date 2020-11-22, issue = 642651572 and reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Plugin hook for instance/database/table metadata · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
731658059 | https://github.com/simonw/datasette/issues/860#issuecomment-731658059 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMTY1ODA1OQ== | simonw 9599 | 2020-11-22T00:31:47Z | 2020-11-22T00:33:48Z | OWNER | Documented behaviour right now, for metadata set at the instance level, is: https://docs.datasette.io/en/stable/metadata.html
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 | |
731657660 | https://github.com/simonw/datasette/issues/860#issuecomment-731657660 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMTY1NzY2MA== | simonw 9599 | 2020-11-22T00:27:32Z | 2020-11-22T00:31:54Z | OWNER | Open question: how should cascading work? If a table is missing a field but the database or instance has it, should that value cascade down to the table? It feels like But... should the other fields cascade? Cascading What about |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 | |
731657486 | https://github.com/simonw/datasette/issues/860#issuecomment-731657486 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMTY1NzQ4Ng== | simonw 9599 | 2020-11-22T00:25:34Z | 2020-11-22T00:25:34Z | OWNER | There are three layers of metadata: table, database and instance. Currently the metadata fields are (ignoring not-quite-metadata like
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plugin hook for instance/database/table metadata 642651572 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [issue] INTEGER REFERENCES [issues]([id]) , [performed_via_github_app] TEXT); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 1