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/304#issuecomment-393610731 | https://api.github.com/repos/simonw/datasette/issues/304 | 393610731 | MDEyOklzc3VlQ29tbWVudDM5MzYxMDczMQ== | 9599 | 2018-05-31T17:29:31Z | 2018-05-31T17:30:05Z | OWNER | I prototyped this a while ago here https://github.com/simonw/datasette/commit/04476ead53758044a5f272ae8696b63d6703115e before we had the ``--config`` mechanism. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
328229224 | |
https://github.com/simonw/datasette/issues/303#issuecomment-393600441 | https://api.github.com/repos/simonw/datasette/issues/303 | 393600441 | MDEyOklzc3VlQ29tbWVudDM5MzYwMDQ0MQ== | 9599 | 2018-05-31T16:56:25Z | 2018-05-31T16:57:41Z | OWNER | Here's a nasty challenge: what happens if a database has the following two tables: * `blah` * `blah.json` What would the URL be for the JSON endpoint for the `blah` table? | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
328172521 | |
https://github.com/simonw/datasette/issues/303#issuecomment-393599840 | https://api.github.com/repos/simonw/datasette/issues/303 | 393599840 | MDEyOklzc3VlQ29tbWVudDM5MzU5OTg0MA== | 9599 | 2018-05-31T16:54:22Z | 2018-05-31T16:54:32Z | OWNER | The interesting thing about this is that it requires URL routing to become aware of the names of all of the available tables. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
328172521 | |
https://github.com/simonw/datasette/issues/294#issuecomment-393557968 | https://api.github.com/repos/simonw/datasette/issues/294 | 393557968 | MDEyOklzc3VlQ29tbWVudDM5MzU1Nzk2OA== | 9599 | 2018-05-31T14:55:46Z | 2018-05-31T14:55:46Z | OWNER | I'm not sure what the best JSON shape for this would be considering the potential complexity of geospatial columns. I do think it's worth exposing these in the inspect JSON though, mainly so Datasette Registry can keep track of all of the openly available geodata out there. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
327365110 | |
https://github.com/simonw/datasette/issues/303#issuecomment-393557406 | https://api.github.com/repos/simonw/datasette/issues/303 | 393557406 | MDEyOklzc3VlQ29tbWVudDM5MzU1NzQwNg== | 9599 | 2018-05-31T14:54:03Z | 2018-05-31T14:54:03Z | OWNER | Our test fixtures currently have a table with a name ending in `.csv`: https://github.com/simonw/datasette/blob/d69ebce53385b7c6fafb85fdab3b136dbf3f332c/tests/fixtures.py#L234-L237 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
328172521 | |
https://github.com/simonw/datasette/issues/297#issuecomment-393554151 | https://api.github.com/repos/simonw/datasette/issues/297 | 393554151 | MDEyOklzc3VlQ29tbWVudDM5MzU1NDE1MQ== | 9599 | 2018-05-31T14:44:37Z | 2018-05-31T14:44:37Z | OWNER | I fixed this in https://github.com/simonw/datasette/commit/b18e4515855c3f1eeca3dfcccdbb6df05869084a | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
327420945 | |
https://github.com/simonw/datasette/issues/294#issuecomment-393549215 | https://api.github.com/repos/simonw/datasette/issues/294 | 393549215 | MDEyOklzc3VlQ29tbWVudDM5MzU0OTIxNQ== | 9599 | 2018-05-31T14:29:37Z | 2018-05-31T14:29:37Z | OWNER | Also of note: `spatialite-test` uses readable strings in the `type` column, while `timezones` has a `geometry_type` column with integers in it. Those integers are documented here: https://www.gaia-gis.it/fossil/libspatialite/wiki?name=switching-to-4.0 ![2018-05-31 at 7 29 am](https://user-images.githubusercontent.com/9599/40788210-5d0f0dd4-64a4-11e8-8141-0386b5c7b384.png) | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
327365110 | |
https://github.com/simonw/datasette/issues/294#issuecomment-393548602 | https://api.github.com/repos/simonw/datasette/issues/294 | 393548602 | MDEyOklzc3VlQ29tbWVudDM5MzU0ODYwMg== | 9599 | 2018-05-31T14:27:41Z | 2018-05-31T14:27:56Z | OWNER | Presumably the difference in primary key structure between those two is caused by the fact that the `spatialite-test` database (actually https://www.gaia-gis.it/spatialite-2.3.1/test-2.3.sqlite.gz downloaded from https://www.gaia-gis.it/spatialite-2.3.1/resources.html ) was created by a much older version of SpatialLite - presumably v2.3.1 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
327365110 | |
https://github.com/simonw/datasette/issues/294#issuecomment-393547960 | https://api.github.com/repos/simonw/datasette/issues/294 | 393547960 | MDEyOklzc3VlQ29tbWVudDM5MzU0Nzk2MA== | 9599 | 2018-05-31T14:25:43Z | 2018-05-31T14:25:43Z | OWNER | SpatialLite columns are actually quite a bit more interesting than this - they also have a `geometry_type` (point, polygon, linestring etc), a `coord_dimension` (usually 2 but can be higher) and an `srid`. For example: https://datasette-publish-spatialite-demo.now.sh/spatialite-test-c88bc35/geometry_columns ![2018-05-31 at 7 22 am](https://user-images.githubusercontent.com/9599/40787843-6f9600ee-64a3-11e8-84e5-64d7cc69603a.png) The SRID here is particularly interesting, because it helps hint at the fact that the results from these queries won't be latitude/longitude co-ordinates - which means that `AsGeoJSON()` won't return results that can be easily rendered by Leaflet: https://datasette-publish-spatialite-demo.now.sh/spatialite-test-c88bc35?sql=select+AsGeoJSON(Geometry)+from+HighWays%20limit1 Compare with https://timezones-api.now.sh/timezones-a99b2e3/geometry_columns: ![2018-05-31 at 7 25 am](https://user-images.githubusercontent.com/9599/40787991-d2650756-64a3-11e8-936e-2dcce7dd1515.png) | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
327365110 | |
https://github.com/simonw/datasette/issues/243#issuecomment-393544357 | https://api.github.com/repos/simonw/datasette/issues/243 | 393544357 | MDEyOklzc3VlQ29tbWVudDM5MzU0NDM1Nw== | 9599 | 2018-05-31T14:14:49Z | 2018-05-31T14:14:49Z | OWNER | Demo: https://datasette-publish-spatialite-demo.now.sh/spatialite-test-c88bc35?sql=select+AsText(Geometry)+from+HighWays+limit+1%3B Published using `datasette publish now --spatialite /tmp/spatialite-test.db` | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
318737808 | |
https://github.com/simonw/datasette/issues/295#issuecomment-393534579 | https://api.github.com/repos/simonw/datasette/issues/295 | 393534579 | MDEyOklzc3VlQ29tbWVudDM5MzUzNDU3OQ== | 9599 | 2018-05-31T13:44:15Z | 2018-05-31T13:44:15Z | OWNER | I actually started doing this in 45e502aace6cc1198cc5f9a04d61b4a1860a012b | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
327383759 |