issue_comments
5 rows where author_association = "OWNER", "created_at" is on date 2020-11-24 and issue = 642651572 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 · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
733288841 | https://github.com/simonw/datasette/issues/860#issuecomment-733288841 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMzI4ODg0MQ== | simonw 9599 | 2020-11-24T23:19:47Z | 2020-11-24T23:20:24Z | OWNER | Here's what I have today - it's an undocumented |
{ "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 | |
733288522 | https://github.com/simonw/datasette/issues/860#issuecomment-733288522 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMzI4ODUyMg== | simonw 9599 | 2020-11-24T23:18:47Z | 2020-11-24T23:18:47Z | OWNER | In #942 I want to add support for per-column metadata - which means this new lookup mechanism will need to be able to answer the question "what description is available for this column". So what should the
|
{ "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 | |
733287619 | https://github.com/simonw/datasette/issues/860#issuecomment-733287619 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMzI4NzYxOQ== | simonw 9599 | 2020-11-24T23:16:21Z | 2020-11-24T23:16:21Z | OWNER | I'll also allow any key to be looked up - so if users want to invent their own metadata keys other than the default |
{ "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 | |
733287416 | https://github.com/simonw/datasette/issues/860#issuecomment-733287416 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMzI4NzQxNg== | simonw 9599 | 2020-11-24T23:15:44Z | 2020-11-24T23:15:44Z | OWNER | I'm going to go with a plugin hook (and Datasette method) that returns individual values - so you ask it for e.g. the The default plugin hook implementation that ships with Datasette will then implement cascading lookups against |
{ "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 | |
733175454 | https://github.com/simonw/datasette/issues/860#issuecomment-733175454 | https://api.github.com/repos/simonw/datasette/issues/860 | MDEyOklzc3VlQ29tbWVudDczMzE3NTQ1NA== | simonw 9599 | 2020-11-24T19:06:07Z | 2020-11-24T19:06:07Z | OWNER | I see two ways this plugin hook could work. It could be asked about a specific instance, database or table and return the full metadata for that object. OR it could ask for a specific metadata field - e.g. The more finely grained one would allow plugins to implement their own cascading rules pretty easily. Is there a reason it would be better for the hook to return an entire block of JSON for a specific table or database? I also need to decide if this hook is just going to be about source/license/about displayed metadata, or if it will include the functionality that has been sneaking into Perhaps I should split those out into a "configuration" concept first, after renaming |
{ "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