issue_comments
3 rows where issue = 505512251
This data as json, CSV (advanced)
Suggested facets: user, author_association, created_at (date), 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: ```json { "databases": { "MYDB": { "tables": { "MYFIRSTTABLE": { "source": "Test", "source_url": "https://www.google.com", "queries": { "Query 1": { "sql": "select * from MYFIRSTTABLE", "title": "Query 1", "description": "This is the first query" } } }, "MYSECONDTABLE": { "source": "Test2", "source_url": "https://www.google.com", "queries": { "Query 2": { "sql": "select * from MYSECONDTABLE;", "title": "Query 2", "description": "This is the second query" } } } } } } } ``` The `"queries" section isn't supported at the table level - it only works at the database level. So that example should look like this: ```json { "databases": { "MYDB": { "tables": { "MYFIRSTTABLE": { "source": "Test", "source_url": "https://www.google.com" }, "MYSECONDTABLE": { "source": "Test2", "source_url": "https://www.google.com" } }, "queries": { "Query 1": { "sql": "select * from MYFIRSTTABLE", "title": "Query 1", "description": "This is the first query" }, "Query 2": { "sql": "select * from MYSECONDTABLE;", "title": "Query 2", "… | {"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 | |
| 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 | |
| 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 |
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]);