issue_comments
5 rows where issue = 1656432059, "updated_at" is on date 2023-07-26 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- WIP new JSON for queries · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1652296467 | https://github.com/simonw/datasette/pull/2053#issuecomment-1652296467 | https://api.github.com/repos/simonw/datasette/issues/2053 | IC_kwDOBm6k_c5ifAsT | simonw 9599 | 2023-07-26T18:26:44Z | 2023-07-26T18:26:44Z | OWNER | I'm abandoning this branch in favour of a fresh attempt, described here: - https://github.com/simonw/datasette/issues/2109 I'll copy bits and pieces of this branch across as-needed. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP new JSON for queries 1656432059 | |
1651904060 | https://github.com/simonw/datasette/pull/2053#issuecomment-1651904060 | https://api.github.com/repos/simonw/datasette/issues/2053 | IC_kwDOBm6k_c5idg48 | simonw 9599 | 2023-07-26T14:19:00Z | 2023-07-26T15:25:15Z | OWNER | Worth noting that the One slight hiccup with that plugin hook is this:
I could turn that into a Datasette defined object that behaves like a sqlite3.Row though, which would give me extra flexibility in the future. A bit tricky though since it's implemented in C for performance: https://github.com/python/cpython/blob/b0202a4e5d6b629ba5acbc703e950f08ebaf07df/Modules/_sqlite/row.c Pasted that into Claude for the following explanation:
I could use protocols in Python to make my own Turned this into a TIL: https://til.simonwillison.net/python/protocols |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP new JSON for queries 1656432059 | |
1651894668 | https://github.com/simonw/datasette/pull/2053#issuecomment-1651894668 | https://api.github.com/repos/simonw/datasette/issues/2053 | IC_kwDOBm6k_c5idemM | simonw 9599 | 2023-07-26T14:14:34Z | 2023-07-26T14:14:34Z | OWNER | Another point of confusion is how I could resolve this by turning the information on the index page into extras, which can optionally be requested any time a query is run but default to being shown if there is no query. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP new JSON for queries 1656432059 | |
1651883505 | https://github.com/simonw/datasette/pull/2053#issuecomment-1651883505 | https://api.github.com/repos/simonw/datasette/issues/2053 | IC_kwDOBm6k_c5idb3x | simonw 9599 | 2023-07-26T14:08:20Z | 2023-07-26T14:08:20Z | OWNER | I think the hardest part of getting this working is dealing with the different formats. Idea: refactor |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP new JSON for queries 1656432059 | |
1651874649 | https://github.com/simonw/datasette/pull/2053#issuecomment-1651874649 | https://api.github.com/repos/simonw/datasette/issues/2053 | IC_kwDOBm6k_c5idZtZ | simonw 9599 | 2023-07-26T14:03:37Z | 2023-07-26T14:03:37Z | OWNER | Big chunk of commented-out code I just removed: ```python
``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP new JSON for queries 1656432059 |
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