issue_comments
5 rows where author_association = "OWNER", "created_at" is on date 2020-03-22 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: issue_url, created_at (date), updated_at (date)
user 1
- simonw 5
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
602150641 | https://github.com/simonw/datasette/issues/650#issuecomment-602150641 | https://api.github.com/repos/simonw/datasette/issues/650 | MDEyOklzc3VlQ29tbWVudDYwMjE1MDY0MQ== | simonw 9599 | 2020-03-22T05:31:13Z | 2020-03-22T05:31:13Z | OWNER | Ansible has a good example of a glossary: https://docs.ansible.com/ansible/latest/reference_appendices/glossary.html |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add a glossary to the documentation 534629631 | |
602140071 | https://github.com/simonw/datasette/issues/698#issuecomment-602140071 | https://api.github.com/repos/simonw/datasette/issues/698 | MDEyOklzc3VlQ29tbWVudDYwMjE0MDA3MQ== | simonw 9599 | 2020-03-22T02:53:48Z | 2020-03-22T02:53:48Z | OWNER | This feature should include the ability to set a custom redirect URL for after the query has been executed - that way it can be used to build things like "delete this row" which redirect back to the correct table. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability for a canned query to write to the database 582517965 | |
602139031 | https://github.com/simonw/datasette/issues/702#issuecomment-602139031 | https://api.github.com/repos/simonw/datasette/issues/702 | MDEyOklzc3VlQ29tbWVudDYwMjEzOTAzMQ== | simonw 9599 | 2020-03-22T02:36:09Z | 2020-03-22T02:36:09Z | OWNER | Found a bug: if you click on a column with a default sort order applied to it you get: "Cannot use _sort and _sort_desc at the same time" |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Option in metadata.json to set default sort order for a table 585390482 | |
602138528 | https://github.com/simonw/datasette/issues/702#issuecomment-602138528 | https://api.github.com/repos/simonw/datasette/issues/702 | MDEyOklzc3VlQ29tbWVudDYwMjEzODUyOA== | simonw 9599 | 2020-03-22T02:29:23Z | 2020-03-22T02:29:23Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Option in metadata.json to set default sort order for a table 585390482 | ||
602122492 | https://github.com/simonw/datasette/issues/702#issuecomment-602122492 | https://api.github.com/repos/simonw/datasette/issues/702 | MDEyOklzc3VlQ29tbWVudDYwMjEyMjQ5Mg== | simonw 9599 | 2020-03-22T00:01:56Z | 2020-03-22T00:01:56Z | OWNER | I'm going to mirror the URL syntax here, so the options in
It will throw an error if you try to define both. If I add the ability to sort by multiple columns in the future (#197) I can allow a list of columns here - though I'm not sure how I would represent "sort by created asc, title desc" in that case. If you want to disable user-specified sorting you can do so using the existing |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Option in metadata.json to set default sort order for a table 585390482 |
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]);
issue 3