issue_comments
8 rows where "created_at" is on date 2019-10-21 sorted by reactions
This data as json, CSV (advanced)
Suggested facets: issue_url, reactions, updated_at (date)
id | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions ▼ | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
544318343 | https://github.com/simonw/datasette/issues/588#issuecomment-544318343 | https://api.github.com/repos/simonw/datasette/issues/588 | MDEyOklzc3VlQ29tbWVudDU0NDMxODM0Mw== | simonw 9599 | 2019-10-21T01:47:11Z | 2019-10-21T01:47:11Z | OWNER | I think I see what's gone wrong here. Here's your example re-indented:
The `"queries" section isn't supported at the table level - it only works at the database level. So that example should look like this:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Queries per DB table in metadata.json 505512251 | |
544318517 | https://github.com/simonw/datasette/issues/260#issuecomment-544318517 | https://api.github.com/repos/simonw/datasette/issues/260 | MDEyOklzc3VlQ29tbWVudDU0NDMxODUxNw== | simonw 9599 | 2019-10-21T01:48:24Z | 2019-10-21T01:48:24Z | OWNER | This came up in #588 - it would be helpful if this would spot things like |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Validate metadata.json on startup 323223872 | |
544318553 | https://github.com/simonw/datasette/issues/588#issuecomment-544318553 | https://api.github.com/repos/simonw/datasette/issues/588 | MDEyOklzc3VlQ29tbWVudDU0NDMxODU1Mw== | simonw 9599 | 2019-10-21T01:48:41Z | 2019-10-21T01:48:41Z | OWNER | Closing this, but #260 would definitely help here. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Queries per DB table in metadata.json 505512251 | |
544320666 | https://github.com/simonw/datasette/pull/603#issuecomment-544320666 | https://api.github.com/repos/simonw/datasette/issues/603 | MDEyOklzc3VlQ29tbWVudDU0NDMyMDY2Ng== | simonw 9599 | 2019-10-21T02:02:48Z | 2019-10-21T02:02:48Z | OWNER | Nice fix, thanks. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
always pop as_format off args dict 509612217 | |
544502617 | https://github.com/simonw/datasette/issues/588#issuecomment-544502617 | https://api.github.com/repos/simonw/datasette/issues/588 | MDEyOklzc3VlQ29tbWVudDU0NDUwMjYxNw== | bsilverm 12617395 | 2019-10-21T12:58:22Z | 2019-10-21T12:58:22Z | NONE | Thanks for the reply. I was hoping queries per table were supported, as I have an application that builds tables depending on the user input to the application. It will either create one table, or two.. and if one or the other is missing, certain queries will return errors. Of course I can work around this by labeling the query name and hope users don't click queries they have not created a table for, but ideally the user would see the queries available based on the tables that exist in their database. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Queries per DB table in metadata.json 505512251 | |
544646516 | https://github.com/dogsheep/genome-to-sqlite/issues/1#issuecomment-544646516 | https://api.github.com/repos/dogsheep/genome-to-sqlite/issues/1 | MDEyOklzc3VlQ29tbWVudDU0NDY0NjUxNg== | simonw 9599 | 2019-10-21T18:30:14Z | 2019-10-21T18:30:14Z | MEMBER | Thanks to help from Dr. Laura Cantino at Science Hack Day San Francisco I've been able to pull together this query:
See also https://www.snpedia.com/index.php/Rs12913832 - in particular this table: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Figure out some interesting example SQL queries 496415321 | |
544648863 | https://github.com/dogsheep/genome-to-sqlite/issues/1#issuecomment-544648863 | https://api.github.com/repos/dogsheep/genome-to-sqlite/issues/1 | MDEyOklzc3VlQ29tbWVudDU0NDY0ODg2Mw== | simonw 9599 | 2019-10-21T18:36:03Z | 2019-10-21T18:36:03Z | MEMBER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Figure out some interesting example SQL queries 496415321 | ||
544335363 | https://github.com/dogsheep/twitter-to-sqlite/issues/20#issuecomment-544335363 | https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/20 | MDEyOklzc3VlQ29tbWVudDU0NDMzNTM2Mw== | simonw 9599 | 2019-10-21T03:32:04Z | 2019-10-21T03:32:04Z | MEMBER | In case anyone is interested, here's an extract from the crontab I'm running these under at the moment:
|
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--since support for various commands for refresh-by-cron 506268945 |
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 5