issue_comments
10 rows where "created_at" is on date 2020-02-22 and reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}"
This data as json, CSV (advanced)
Suggested facets: author_association
id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
589897959 | https://github.com/simonw/datasette/issues/678#issuecomment-589897959 | https://api.github.com/repos/simonw/datasette/issues/678 | MDEyOklzc3VlQ29tbWVudDU4OTg5Nzk1OQ== | simonw 9599 | 2020-02-22T01:02:47Z | 2020-02-22T01:02:47Z | OWNER | While I'm at it, the hook should accept an optional `database` name argument as well. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | prepare_connection() plugin hook should accept optional datasette argument 569253072 | |
589908060 | https://github.com/simonw/datasette/issues/678#issuecomment-589908060 | https://api.github.com/repos/simonw/datasette/issues/678 | MDEyOklzc3VlQ29tbWVudDU4OTkwODA2MA== | simonw 9599 | 2020-02-22T02:28:51Z | 2020-02-22T02:28:51Z | OWNER | Done. Updated documentation is here: https://datasette.readthedocs.io/en/latest/plugins.html#prepare-connection-conn-database-datasette | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | prepare_connection() plugin hook should accept optional datasette argument 569253072 | |
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 `_search_wildcard=` URL parameter be worth supporting I wonder? What's your specific use-case for wildcards? | {"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 | |
589908363 | https://github.com/simonw/datasette/pull/669#issuecomment-589908363 | https://api.github.com/repos/simonw/datasette/issues/669 | MDEyOklzc3VlQ29tbWVudDU4OTkwODM2Mw== | simonw 9599 | 2020-02-22T02:32:00Z | 2020-02-22T02:32:00Z | OWNER | Thanks for spotting this! | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | fix db-to-sqlite command in ecosystem doc page 563348959 | |
589908465 | https://github.com/simonw/datasette/pull/666#issuecomment-589908465 | https://api.github.com/repos/simonw/datasette/issues/666 | MDEyOklzc3VlQ29tbWVudDU4OTkwODQ2NQ== | simonw 9599 | 2020-02-22T02:33:18Z | 2020-02-22T02:33:18Z | OWNER | This is a smart optimization. I'd like to add a test for it, since the logic is a tiny bit more complex. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use inspect-file, if possible, for total row count 562085508 | |
589909401 | https://github.com/simonw/datasette/issues/679#issuecomment-589909401 | https://api.github.com/repos/simonw/datasette/issues/679 | MDEyOklzc3VlQ29tbWVudDU4OTkwOTQwMQ== | simonw 9599 | 2020-02-22T02:43:42Z | 2020-02-22T02:46:16Z | OWNER | Before shipping there are a few additions I can make to the https://datasette.readthedocs.io/en/stable/ecosystem.html page: * https://github.com/simonw/shapefile-to-sqlite * https://github.com/simonw/datasette-mask-columns (which will itself depend on 0.36 being out) * https://github.com/simonw/datasette-auth-existing-cookies * https://github.com/simonw/datasette-sentry I could also add links to associated blog entries directly to those descriptions on the ecosystem page: * https://simonwillison.net/2020/Jan/29/weeknotes-datasette-cookies-sentry/ * https://simonwillison.net/2020/Feb/19/shapefile-to-sqlite/ | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Release 0.36 569268612 | |
589914711 | https://github.com/simonw/datasette/issues/680#issuecomment-589914711 | https://api.github.com/repos/simonw/datasette/issues/680 | MDEyOklzc3VlQ29tbWVudDU4OTkxNDcxMQ== | simonw 9599 | 2020-02-22T03:51:47Z | 2020-02-22T03:51:47Z | OWNER | I considered just updating the GitHub release with a link to the release notes, but I'm building other things against the GitHub releases API such that it's nicer to have the release notes live there. I bet I could use pandoc to automate the conversion of the formats in one or other direction. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Release automation: automate the bit that posts the GitHub release 569275763 | |
589914753 | https://github.com/simonw/datasette/issues/679#issuecomment-589914753 | https://api.github.com/repos/simonw/datasette/issues/679 | MDEyOklzc3VlQ29tbWVudDU4OTkxNDc1Mw== | simonw 9599 | 2020-02-22T03:52:13Z | 2020-02-22T03:52:13Z | OWNER | https://datasette.readthedocs.io/en/stable/changelog.html#v0-36 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Release 0.36 569268612 | |
589914811 | https://github.com/simonw/datasette/issues/678#issuecomment-589914811 | https://api.github.com/repos/simonw/datasette/issues/678 | MDEyOklzc3VlQ29tbWVudDU4OTkxNDgxMQ== | simonw 9599 | 2020-02-22T03:53:07Z | 2020-02-22T03:53:19Z | OWNER | Shipped in 0.36 https://datasette.readthedocs.io/en/stable/changelog.html#v0-36 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | prepare_connection() plugin hook should accept optional datasette argument 569253072 | |
589922016 | https://github.com/simonw/datasette/issues/676#issuecomment-589922016 | https://api.github.com/repos/simonw/datasette/issues/676 | MDEyOklzc3VlQ29tbWVudDU4OTkyMjAxNg== | tunguyenatwork 58088336 | 2020-02-22T05:50:10Z | 2020-02-22T05:50:10Z | NONE | Thanks Simon, My use case is using Datasette for full text search type ahead. That was working pretty well. The _search_wildcard= option will be awesome. Thanks | {"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]);