issue_comments
5 rows where issue = 1114628238
This data as json, CSV (advanced)
Suggested facets: reactions, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
1021860694 | https://github.com/simonw/datasette/issues/1613#issuecomment-1021860694 | https://api.github.com/repos/simonw/datasette/issues/1613 | IC_kwDOBm6k_c486FtW | simonw 9599 | 2022-01-26T04:57:53Z | 2022-01-26T04:57:53Z | OWNER | The existing flow where you can apply filters to a table and then click "View and edit SQL" to see the query is a good starting point. Group by queries are both crucially important and difficult to assemble for beginners. Providing a way to see the query that was used by a facet (since facets are really just group-by-counts) would be very useful, which could come out of this: - #1080 | {"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Improvements to help make Datasette a better tool for learning SQL 1114628238 | |
1022254258 | https://github.com/simonw/datasette/issues/1613#issuecomment-1022254258 | https://api.github.com/repos/simonw/datasette/issues/1613 | IC_kwDOBm6k_c487lyy | simonw 9599 | 2022-01-26T14:33:46Z | 2022-01-26T14:37:31Z | OWNER | Tool for setting up foreign key relationships. It could even verify the relationship before you apply it - checking that every value in the column does indeed correspond to a value in the other table. Could also detect and suggest possible ones. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Improvements to help make Datasette a better tool for learning SQL 1114628238 | |
1022255862 | https://github.com/simonw/datasette/issues/1613#issuecomment-1022255862 | https://api.github.com/repos/simonw/datasette/issues/1613 | IC_kwDOBm6k_c487mL2 | simonw 9599 | 2022-01-26T14:35:31Z | 2022-01-26T14:37:44Z | OWNER | Joins are really hard. A mechanism for constructing them in the table view would help a lot: - https://github.com/simonw/datasette/issues/613 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Improvements to help make Datasette a better tool for learning SQL 1114628238 | |
1022257496 | https://github.com/simonw/datasette/issues/1613#issuecomment-1022257496 | https://api.github.com/repos/simonw/datasette/issues/1613 | IC_kwDOBm6k_c487mlY | simonw 9599 | 2022-01-26T14:37:14Z | 2022-01-26T14:37:14Z | OWNER | Better contextual help on the SQL editor - like in Django SQL Dashboard which shows all available tables and columns. Fancy inline autocomplete would be great too, but that's pretty hard for SQL based on past research. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Improvements to help make Datasette a better tool for learning SQL 1114628238 | |
1022381732 | https://github.com/simonw/datasette/issues/1613#issuecomment-1022381732 | https://api.github.com/repos/simonw/datasette/issues/1613 | IC_kwDOBm6k_c488E6k | simonw 9599 | 2022-01-26T16:41:45Z | 2022-01-26T16:41:45Z | OWNER | A better interface for modifying the columns used in the SELECT clause would be useful too. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Improvements to help make Datasette a better tool for learning SQL 1114628238 |
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]);