issue_comments
2 rows where issue = 509340359 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date)
issue 1
- Don't auto-format SQL on page load · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
544014518 | https://github.com/simonw/datasette/pull/601#issuecomment-544014518 | https://api.github.com/repos/simonw/datasette/issues/601 | MDEyOklzc3VlQ29tbWVudDU0NDAxNDUxOA== | simonw 9599 | 2019-10-18T23:57:44Z | 2019-10-18T23:57:44Z | OWNER | That's a good idea. It could even be smart about it and only show the "Format SQL" button on that page of the output of the function would differ from what's there already. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Don't auto-format SQL on page load 509340359 | |
543986312 | https://github.com/simonw/datasette/pull/601#issuecomment-543986312 | https://api.github.com/repos/simonw/datasette/issues/601 | MDEyOklzc3VlQ29tbWVudDU0Mzk4NjMxMg== | simonw 9599 | 2019-10-18T22:38:00Z | 2019-10-18T22:38:00Z | OWNER | @rixx does this look like the right way to do #600 to you? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Don't auto-format SQL on page load 509340359 |
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]);
user 1