issue_comments
1 row where issue_url = "https://api.github.com/repos/simonw/datasette/issues/1757" and "updated_at" is on date 2022-09-06
This data as json, CSV (advanced)
Suggested facets: 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
1237553237 | https://github.com/simonw/datasette/pull/1757#issuecomment-1237553237 | https://api.github.com/repos/simonw/datasette/issues/1757 | IC_kwDOBm6k_c5Jw5BV | simonw 9599 | 2022-09-06T00:51:21Z | 2022-09-06T00:51:21Z | OWNER | Interesting feature idea. It's a weird edge-case, but it's the kind of thing I worry about: what if the user has a column called `*`? This is technically allowed in SQLite, even though it's vastly unlikely. On that basis, I think `?_json_all=1` would be a better design here than `?_json=*` - since it removes any possible ambiguity. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | feat: add a wildcard for _json columns 1268121674 |
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]);