issue_comments
6 rows where "created_at" is on date 2018-05-26, reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw · 6 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
392288531 | https://github.com/simonw/datasette/issues/288#issuecomment-392288531 | https://api.github.com/repos/simonw/datasette/issues/288 | MDEyOklzc3VlQ29tbWVudDM5MjI4ODUzMQ== | simonw 9599 | 2018-05-26T21:14:37Z | 2019-04-15T23:01:17Z | OWNER | This might also be an opportunity to support an __in= operator - though that's an odd one as it acts equivalent to an OR whereas every other parameter is combined with an AND UPDATE 15th April 2019: I implemented |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support multiple filters of the same type 326767626 | |
392291716 | https://github.com/simonw/datasette/issues/289#issuecomment-392291716 | https://api.github.com/repos/simonw/datasette/issues/289 | MDEyOklzc3VlQ29tbWVudDM5MjI5MTcxNg== | simonw 9599 | 2018-05-26T22:22:47Z | 2018-05-26T22:22:47Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
?_ttl= parameter to control caching 326768188 | ||
392291605 | https://github.com/simonw/datasette/issues/289#issuecomment-392291605 | https://api.github.com/repos/simonw/datasette/issues/289 | MDEyOklzc3VlQ29tbWVudDM5MjI5MTYwNQ== | simonw 9599 | 2018-05-26T22:20:02Z | 2018-05-26T22:20:02Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
?_ttl= parameter to control caching 326768188 | ||
392288990 | https://github.com/simonw/datasette/issues/289#issuecomment-392288990 | https://api.github.com/repos/simonw/datasette/issues/289 | MDEyOklzc3VlQ29tbWVudDM5MjI4ODk5MA== | simonw 9599 | 2018-05-26T21:24:10Z | 2018-05-26T21:24:10Z | OWNER | An example of a query where you might want to use this option: https://fivethirtyeight.datasettes.com/fivethirtyeight-5de27e3?sql=select+rowid%2C+*+from+%5Balcohol-consumption%2Fdrinks%5D+order+by+random%28%29+limit+1 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
?_ttl= parameter to control caching 326768188 | |
392279644 | https://github.com/simonw/datasette/issues/276#issuecomment-392279644 | https://api.github.com/repos/simonw/datasette/issues/276 | MDEyOklzc3VlQ29tbWVudDM5MjI3OTY0NA== | simonw 9599 | 2018-05-26T18:34:21Z | 2018-05-26T18:34:21Z | OWNER | I've been thinking a bit about modifying the SQL select statement used for the table view recently. I've run into a few examples of SQLite database that slow to a crawl when viewed with datasette because the rows are too big, so there's definitely scope for supporting custom select clauses (avoiding some columns, showing length(colname) for others). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Handle spatialite geometry columns better 324835838 | |
392279508 | https://github.com/simonw/datasette/issues/276#issuecomment-392279508 | https://api.github.com/repos/simonw/datasette/issues/276 | MDEyOklzc3VlQ29tbWVudDM5MjI3OTUwOA== | simonw 9599 | 2018-05-26T18:32:07Z | 2018-05-26T18:32:07Z | OWNER | Related: I started the documentation for using SpatiaLite with Datasette here: https://datasette.readthedocs.io/en/latest/spatialite.html |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Handle spatialite geometry columns better 324835838 |
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