issue_comments
2 rows where author_association = "OWNER", issue = 539590148 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- fts5 syntax error when using punctuation · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
568269476 | https://github.com/simonw/datasette/issues/651#issuecomment-568269476 | https://api.github.com/repos/simonw/datasette/issues/651 | MDEyOklzc3VlQ29tbWVudDU2ODI2OTQ3Ng== | simonw 9599 | 2019-12-22T14:46:37Z | 2019-12-22T14:47:03Z | OWNER | https://stackoverflow.com/a/43756146 says that an escaping mechanism that works is this one:
So split on whitespace and then encapsulate each search term in double quotes. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fts5 syntax error when using punctuation 539590148 | |
568268746 | https://github.com/simonw/datasette/issues/651#issuecomment-568268746 | https://api.github.com/repos/simonw/datasette/issues/651 | MDEyOklzc3VlQ29tbWVudDU2ODI2ODc0Ng== | simonw 9599 | 2019-12-22T14:37:37Z | 2019-12-22T14:37:37Z | OWNER | I've not yet been able to figure out what the escaping rule are for FTS5 queries. If we figure out how those work maybe we can bundle them as a custom function?
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fts5 syntax error when using punctuation 539590148 |
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