issue_comments
3 rows where "created_at" is on date 2020-11-22 sorted by issue_url
This data as json, CSV (advanced)
id | html_url | issue_url ▼ | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
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 `sort` and `sort_desc`): - `title` - `description` (or `description_html`) - `about` / `about_url` - `source` / `source_url` - `license` / `license_url` | {"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 `license` should definitely cascade: if an instance lists a certain `license` that should absolutely filter through to all databases and tables. But... should the other fields cascade? Cascading `description` doesn't feel right at all, and neither does `title`. What about `about` and `about_url` and `source` and `source_url`? I'm a bit torn on whether they should cascade or not. I'm leaning towards cascading them. | {"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 | |
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 > The above metadata will be displayed on the index page of your Datasette-powered site. The source and license information will also be included in the footer of every page served by Datasette. > > ... > > Metadata at the top level of the JSON will be shown on the index page and in the footer on every page of the site. The license and source is expected to apply to all of your data. | {"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]);
updated_at (date) 1 ✖