issue_comments
4 rows where "updated_at" is on date 2019-01-17 sorted by id descending
This data as json, CSV (advanced)
Suggested facets: issue
created_at (date) 1 ✖
id ▲ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
455231411 | https://github.com/simonw/datasette/issues/402#issuecomment-455231411 | https://api.github.com/repos/simonw/datasette/issues/402 | MDEyOklzc3VlQ29tbWVudDQ1NTIzMTQxMQ== | simonw 9599 | 2019-01-17T16:15:21Z | 2019-01-17T16:15:21Z | OWNER | Unfortunately it looks like there isn't currently a mechanism in the Python sqlite3 library for setting configuration flags like SQLITE_DBCONFIG_DEFENSIVE | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use SQLITE_DBCONFIG_DEFENSIVE plus other recommendations from SQLite security docs 400340905 | |
455230501 | https://github.com/simonw/datasette/issues/401#issuecomment-455230501 | https://api.github.com/repos/simonw/datasette/issues/401 | MDEyOklzc3VlQ29tbWVudDQ1NTIzMDUwMQ== | simonw 9599 | 2019-01-17T16:12:59Z | 2019-01-17T16:12:59Z | OWNER | Datasette-cluster-map doesn't use the new plugin configuration mechanism yet - it really should! The best example of how to use this mechanism right now is embedded in the Datasette unit tests: https://github.com/simonw/datasette/blob/b7257a21bf3dfa7353980f343c83a616da44daa7/tests/fixtures.py#L266-L270 https://github.com/simonw/datasette/blob/b7257a21bf3dfa7353980f343c83a616da44daa7/tests/test_plugins.py#L139-L145 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | How to pass configuration to plugins? 400229984 | |
455224327 | https://github.com/simonw/datasette/issues/402#issuecomment-455224327 | https://api.github.com/repos/simonw/datasette/issues/402 | MDEyOklzc3VlQ29tbWVudDQ1NTIyNDMyNw== | simonw 9599 | 2019-01-17T15:56:57Z | 2019-01-17T15:56:57Z | OWNER | https://sqlite.org/security.html has other recommmendations for apps that accept SQLite files from untrusted sources that we should apply. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use SQLITE_DBCONFIG_DEFENSIVE plus other recommendations from SQLite security docs 400340905 | |
455223551 | https://github.com/simonw/datasette/issues/402#issuecomment-455223551 | https://api.github.com/repos/simonw/datasette/issues/402 | MDEyOklzc3VlQ29tbWVudDQ1NTIyMzU1MQ== | simonw 9599 | 2019-01-17T15:55:06Z | 2019-01-17T15:55:06Z | OWNER | It's new in SQLite 3.26.0 so I will need to figure out how to only apply it in that version or higher. https://sqlite.org/releaselog/3_26_0.html | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Use SQLITE_DBCONFIG_DEFENSIVE plus other recommendations from SQLite security docs 400340905 |
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]);
updated_at (date) 1 ✖