issue_comments
1 row where author_association = "OWNER", issue = 568091133 and "updated_at" is on date 2020-02-22 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- ?_searchmode=raw option for running FTS searches without escaping characters · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
589908293 | https://github.com/simonw/datasette/issues/676#issuecomment-589908293 | https://api.github.com/repos/simonw/datasette/issues/676 | MDEyOklzc3VlQ29tbWVudDU4OTkwODI5Mw== | simonw 9599 | 2020-02-22T02:31:21Z | 2020-02-22T02:31:21Z | OWNER | I'm afraid this is by design: supporting wildcards in that mode was more-or-less accidental and often resulted in unexpected user-facing syntax errors when users accidentally entered search text that included characters with special meaning to SQLite. You can still execute wildcard searches but you have to do so using custom SQL statements. I'm open to suggestions for more friendly ways to support this functionality. Would an alternative |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
?_searchmode=raw option for running FTS searches without escaping characters 568091133 |
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