issue_comments
9 rows where issue = 735532751 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- sqlite-utils search command · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
722054264 | https://github.com/simonw/sqlite-utils/issues/192#issuecomment-722054264 | https://api.github.com/repos/simonw/sqlite-utils/issues/192 | MDEyOklzc3VlQ29tbWVudDcyMjA1NDI2NA== | simonw 9599 | 2020-11-05T00:44:39Z | 2020-11-05T00:44:39Z | OWNER | I want This means I need to be able to introspect and tell if a table is FTS4 or FTS5. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils search command 735532751 | |
721453779 | https://github.com/simonw/sqlite-utils/issues/192#issuecomment-721453779 | https://api.github.com/repos/simonw/sqlite-utils/issues/192 | MDEyOklzc3VlQ29tbWVudDcyMTQ1Mzc3OQ== | simonw 9599 | 2020-11-04T00:59:24Z | 2020-11-04T00:59:36Z | OWNER | FTS5 was added in SQLite 3.9.0 in 2015-10-14 - so about a year after CTEs, which means CTEs will always be safe to use with FTS5 queries. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils search command 735532751 | |
721420907 | https://github.com/simonw/sqlite-utils/issues/192#issuecomment-721420907 | https://api.github.com/repos/simonw/sqlite-utils/issues/192 | MDEyOklzc3VlQ29tbWVudDcyMTQyMDkwNw== | simonw 9599 | 2020-11-03T23:07:01Z | 2020-11-03T23:07:01Z | OWNER | I could depend on my Or I could say that only |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils search command 735532751 | |
721420539 | https://github.com/simonw/sqlite-utils/issues/192#issuecomment-721420539 | https://api.github.com/repos/simonw/sqlite-utils/issues/192 | MDEyOklzc3VlQ29tbWVudDcyMTQyMDUzOQ== | simonw 9599 | 2020-11-03T23:05:53Z | 2020-11-03T23:05:53Z | OWNER | Just realized there's a problem with the SQL I am using here: joining to get |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils search command 735532751 | |
721319602 | https://github.com/simonw/sqlite-utils/issues/192#issuecomment-721319602 | https://api.github.com/repos/simonw/sqlite-utils/issues/192 | MDEyOklzc3VlQ29tbWVudDcyMTMxOTYwMg== | simonw 9599 | 2020-11-03T19:05:05Z | 2020-11-03T19:05:05Z | OWNER | Relevant example using a SQLite CTE: https://github.com/simonw/datasette/issues/268#issuecomment-675725464 CTEs were added in SQLite 3.8.3 in 2014-02-03 so they should be safe to use. If someone tries to run |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils search command 735532751 |
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