sha,message,author_date,committer_date,raw_author,raw_committer,repo,author,committer
7a4da7e5aedff3f61648d5530c4dc34de011ea8a,"Documentation for custom SQL queries

http://datasette.readthedocs.io/en/latest/sql_queries.html

Closes #20",2017-12-05T17:43:59Z,2017-12-05T17:43:59Z,13ae486343ea6454a93114c6f558ffea2f2c6874,13ae486343ea6454a93114c6f558ffea2f2c6874,107914493,9599,9599
b7b590b4149563ec6572f577632d7471b84dcb94,"Docs for query.html CSS/template, refs #20",2017-12-05T16:35:14Z,2017-12-05T16:35:14Z,13ae486343ea6454a93114c6f558ffea2f2c6874,13ae486343ea6454a93114c6f558ffea2f2c6874,107914493,9599,9599
a743cdeafca0e5d011c282a53baf753c85d01516,"Canned query support + database/query template refactor

Named canned queries can now be defined in metadata.json like this:

    {
        ""databases"": {
            ""timezones"": {
                ""queries"": {
                    ""timezone_for_point"": ""select tzid from timezones ...""
                }
            }
        }
    }

These will be shown in a new ""Queries"" section beneath ""Views"" on the database page.

As part of this, I refactored the logic for the database index page. It used
to combine the functionality for listing available tables and the
functionality for executing custom SQL queries in a single template and view.
I have split that template out into database.html and query.html and reworked
the view to more clearly separate the custom SQL executing code.

Refs #20",2017-12-05T16:17:02Z,2017-12-05T16:17:02Z,13ae486343ea6454a93114c6f558ffea2f2c6874,13ae486343ea6454a93114c6f558ffea2f2c6874,107914493,9599,9599