issue_comments

The more time I spend with SpatiaLite the more convinced I am that this should be default behavior. There's nothing useful about the binary Geometry representation - it's not even valid WKB. I'm on board with WKT as the default display in HTML and GeoJSON as the default for .json

Should the tablename ones also work for views and canned queries? Probably not.

Since #275 will allow configs to be overridden at the table and database level it also makes sense to expose a completely evaluated list of configs at:

• /dbname/-/config
• /dbname/tablename/-/config

Similar to https://fivethirtyeight.datasettes.com/-/config

Creating URLs using concatenation as seen in ('https://twitter.com/' || user) as user_url is likely to have all sorts of useful applications for ad-hoc analysis.

Do you have an existing example with views?

Just about to ask for this! Move this page https://github.com/simonw/datasette/wiki/Datasettes

into a datasette, with some concept of versioning as well.

I ran an informal survey on twitter and most people were on 3.21 - https://twitter.com/simonw/status/1001487546289815553

Maybe this is from upgrading to the latest OS X release.

Python standard-library SQLite dynamically links against the system sqlite3. So presumably you installed a more up-to-date sqlite3 somewhere on your LD_LIBRARY_PATH.

To compile a statically-linked pysqlite you need to include an amalgamation in the project root when building the extension. Read the relevant setup.py.

I haven't had time to look further into this, but if doing this as a plugin results in useful hooks then I think we should do it that way. We could always require the plugin as a standard dependency.

I think this is going to result in quite a bit of refactoring anyway so it's a good time to add hooks regardless.

On the other hand, if we have to add lots of specialist hooks for it then maybe it's worth integrating into the core.

I don't know how it happened, but I've somehow got myself into a state where my local SQLite for Python 3 on OS X is 3.23.1:

``` ~ $ python3 Python 3.6.5 (default, Mar 30 2018, 06:41:53) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.39.2)] on darwin Type "help", "copyright", "credits" or "license" for more information.

import sqlite3 sqlite3.connect(':memory:').execute('select sqlite_version()').fetchall() [('3.23.1',)]

``` Maybe I did something in homebrew that changed this? I'd love to understand what exactly I did to get to this state.

I'm coming round to the idea that this should be baked into Datasette core - see above referenced issues for some of the explorations I've been doing around this area.

Datasette should absolutely work without SpatiaLite, but it's such a huge bonus part of the SQLite ecosystem that I'm happy to ship features that take advantage of it without being relegated to plugins.

I'm also becoming aware that there aren't really that many other interesting loadable extensions for SQLite. If SpatiaLite was one of dozens I'd feel that a rule that "anything dependent on an extension lives in a plugin" would make sense, but as it stands I think 99% of the time the only loadable extensions people will be using will be SpatiaLite and json1 (and json1 is available in the amalgamation anyway).