github
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/simonw/datasette/issues/402#issuecomment-455231411 | https://api.github.com/repos/simonw/datasette/issues/402 | 455231411 | MDEyOklzc3VlQ29tbWVudDQ1NTIzMTQxMQ== | 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 } |
400340905 | |
https://github.com/simonw/datasette/issues/402#issuecomment-455224327 | https://api.github.com/repos/simonw/datasette/issues/402 | 455224327 | MDEyOklzc3VlQ29tbWVudDQ1NTIyNDMyNw== | 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 } |
400340905 | |
https://github.com/simonw/datasette/issues/402#issuecomment-455223551 | https://api.github.com/repos/simonw/datasette/issues/402 | 455223551 | MDEyOklzc3VlQ29tbWVudDQ1NTIyMzU1MQ== | 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 } |
400340905 |