issues

Table actions

8 rows where "created_at" is on date 2017-11-14 and user = 9599 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: comments, created_at (date), updated_at (date), closed_at (date)

type 1

state 1

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association pull_request body repo type active_lock_reason performed_via_github_app reactions draft state_reason
273709194 MDU6SXNzdWUyNzM3MDkxOTQ= 87 Configure Travis to release new tags to PyPI simonw 9599 closed 0     1 2017-11-14T08:44:08Z 2018-07-10T17:49:13Z 2018-07-10T17:49:12Z OWNER   datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/87/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
273878873 MDU6SXNzdWUyNzM4Nzg4NzM= 91 Option to serve databases from a different prefix, serve regular content elsewhere simonw 9599 closed 0     1 2017-11-14T17:32:46Z 2017-12-10T03:07:58Z 2017-12-10T03:07:53Z OWNER  

It would be useful if the databases themselves could be served from a prefix e.g.

datasette serve mydb.db --path-prefix=db

Now my database is at http://localhost:8001/db/mydb-23423

This would free up the rest of the URL namespace for other things. Maybe we could have an option to serve static content from a known folder e.g.

datasette serve mydb.db --path-prefix=db --root-content=~/my-project/static

Now a hit to http://localhost:8001/news/ serves content from ~/my-project/static/news/index.html

This would make it trivial to package up entire HTML/CSS/JS apps with one or more underlying SQLite databases. Running without --cors would be fine here because any JS apps would be hosted on the same origin.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/91/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
273846123 MDU6SXNzdWUyNzM4NDYxMjM= 90 datasette publish heroku simonw 9599 closed 0     8 2017-11-14T16:01:39Z 2017-12-10T03:06:34Z 2017-12-10T03:05:48Z OWNER  

Heroku has Docker container support so this should not be too hard:

https://devcenter.heroku.com/articles/container-registry-and-runtime

See also #59

This should work exactly like the existing “datasette publish now....” command except it would be “datasette publish heroku...”

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/90/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
273703829 MDU6SXNzdWUyNzM3MDM4Mjk= 86 Filter UI on table page simonw 9599 closed 0   Foreign key edition 2919870 10 2017-11-14T08:22:43Z 2017-11-23T20:34:32Z 2017-11-23T20:34:32Z OWNER  

A UI for building up simple table queries by adding additional filter rules that get executed as query parameters in the URL.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/86/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
273678673 MDU6SXNzdWUyNzM2Nzg2NzM= 85 Detect foreign keys and use them to link HTML pages together simonw 9599 closed 0   Foreign key edition 2919870 6 2017-11-14T06:12:05Z 2017-11-19T06:08:19Z 2017-11-19T06:08:19Z OWNER  

https://stackoverflow.com/a/44430157/6083 documents the PRAGMA needed to extract foreign key references for a table.

At a minimum we can link column values known to be foreign keys to the corresponding row page. We could try to summarize the linked row in some way too - somehow extracting a sensible link title, maybe based on additional configuration in the metadata.json file.

Still todo:

  • [x] Fix it to csvs-to-sqlite refactoring command correctly creates primary key on generated tables
  • [x] Ship new csvs-to-sqlite with refactoring command
  • [x] Refactor column logic to be more predictable in our templates (the rowid special case)
  • [x] Mechanism by which table metadata can specify the "label" column for a table
  • [x] Automatically set the label column as the first column that isn't a primary key (falling back on primary key)
  • [x] Code which runs a "select id, label from table where id in (...)" query as part of the tableview and populates a lookup dictionary
  • [x] Modify templates to use values from that lookup dictionary
 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/85/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
273660425 MDU6SXNzdWUyNzM2NjA0MjU= 84 datasette package --metadata does not work with a relative path simonw 9599 closed 0     0 2017-11-14T04:00:50Z 2017-11-15T05:18:35Z 2017-11-15T05:18:35Z OWNER   
$ datasette package ~/parlgov-db/parlgov.db --metadata=~/parlgov-db/parlgov.json
Usage: datasette package [OPTIONS] FILES...

Error: Invalid value for "-m" / "--metadata": Could not open file: ~/parlgov-db/parlgov.json: No such file or directory

simonw-07542:~ simonw$ cd ~/parlgov-db/
simonw-07542:parlgov-db simonw$ datasette package ~/parlgov-db/parlgov.db --metadata=parlgov.json
Sending build context to Docker daemon   4.46MB
Step 1/7 : FROM python:3
datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/84/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
273895344 MDU6SXNzdWUyNzM4OTUzNDQ= 92 Add --license --license_url --source --source_url --title arguments to datasette publish simonw 9599 closed 0     0 2017-11-14T18:27:07Z 2017-11-15T05:04:41Z 2017-11-15T05:04:41Z OWNER  

I keep on using the echo '{"source": "..."}' | datasette publish now --metadata=- pattern, which suggests it makes sense for us to support these as optional arguments.

https://gist.github.com/simonw/9f8bf23b37a42d7628c4dcc4bba10253

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/92/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
273626815 MDU6SXNzdWUyNzM2MjY4MTU= 83 Individual row view is broken simonw 9599 closed 0     0 2017-11-14T00:29:11Z 2017-11-14T00:45:34Z 2017-11-14T00:45:34Z OWNER   datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/83/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [pull_request] TEXT,
   [body] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
, [active_lock_reason] TEXT, [performed_via_github_app] TEXT, [reactions] TEXT, [draft] INTEGER, [state_reason] TEXT);
CREATE INDEX [idx_issues_repo]
                ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
                ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
                ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
                ON [issues] ([user]);