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/466#issuecomment-491548189 | https://api.github.com/repos/simonw/datasette/issues/466 | 491548189 | MDEyOklzc3VlQ29tbWVudDQ5MTU0ODE4OQ== | 9599 | 2019-05-11T22:21:40Z | 2019-05-11T22:21:47Z | OWNER | This is a little bit tricky. This SQL looks like it may detect Spatialite tables: ```sql select * from sqlite_master where type = "table" and sql like "%CREATE VIRTUAL TABLE%" and sql like "%USING VirtualSpatialIndex%" ``` But where to put it? I think this should go in a new "checks" mechanism, where we run checks against every connected database on Datasette startup. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
443040665 | |
https://github.com/simonw/datasette/issues/466#issuecomment-491549929 | https://api.github.com/repos/simonw/datasette/issues/466 | 491549929 | MDEyOklzc3VlQ29tbWVudDQ5MTU0OTkyOQ== | 9599 | 2019-05-11T22:55:23Z | 2019-05-11T22:55:23Z | OWNER | To build a unit test for this I'm going to have to ship a small spatialite.db binary database as part of the git repo. This is because I need the tests to run even when the spatialite module is not available - but you cannot create a spatialite database without having access to that module. I'll include a build script in the repo for constructing that database. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
443040665 |