issue_comments

This needs to incorporate a sensible way of presenting custom SQL query results too. And let's get a textarea in there for executing SQL while we're at it.

I'm closing #50 - more tests will be added in the future, but the framework is neatly in place for them now.

I'm going to bundle sql and sql_params together into a query nested object like this:

{
    "query": {
        "sql": "select ...",
        "params": {
            "p0": "blah"
        }
    }
}

Closing this, opening a fresh ticket for the navigation stuff.

"parlgov-development.db": {
    "url": "http://www.parlgov.org/"
},
"nhsadmin.sqlite": {
    "url": "https://github.com/psychemedia/openHealthDataDoodles"
}

I’m going to solve this by making it an optional argument you can pass to the serve command. Then the Dockerfile can still build and use it but it won’t interfere with tests or dev.

If argument is not passed, we will calculate hashes on startup and calculate table row counts on demand.

See also #14

The plugin system can also allow alternative providers for the publish command - e.g. maybe hook up hyper.sh as an option for publishing containers.

Still needed:

• [ ] A link to the homepage from some kind of navigation bar in the header
• [ ] link to github.com/simonw/datasette in the footer
• [ ] Slightly better titles (maybe ditch the visited link colours for titles only? should keep those for primary key links)
• [ ] Links to the .json and .jsono versions of every view

http://2016.padjo.org/tutorials/data-primer-census-acs1-demographics/ has a sqlite database: http://2016.padjo.org/files/data/starterpack/census-acs-1year/acs-1-year-2015.sqlite

I tested this by deploying it here: https://datasette-fewuggrvwr.now.sh/

I'm happy with this now that I've implemented the publish command in #26

I can create the temporary directory like so:

import tempfile
t = tempfile.TemporaryDirectory()
t
<TemporaryDirectory '/var/folders/w9/0xm39tk94ng9h52g06z4b54c0000gp/T/tmpkym70wlp'>
t.name
'/var/folders/w9/0xm39tk94ng9h52g06z4b54c0000gp/T/tmpkym70wlp'

And then to delete it all:

t.cleanup()

Doing this works:

import os
os.link('/tmp/databases/northwind.db', '/tmp/tmp-blah/northwind.db')

That creates a link in tmp-blah - and then when I delete that entire directory like so:

import shutil
shutil.rmtree('/tmp/tmp-blah')

The original database is not deleted, just the link.

Simplest version of this:

1. Create a temporary directory
2. Write a Dockerfile into it that pulls an image and pip installs datasette
3. Add symlinks to the DBs they listed (so we don't have to copy them)
4. Shell out to "now"
5. Done!

I can detect something is a view like this:

SELECT name from sqlite_master WHERE type ='view';

Here's what a table looks like now at a smaller screen size: