home / github

Menu
  • Search all tables
  • GraphQL API

issues

Table actions
  • GraphQL API for issues

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

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

  • issue 14

state 1

  • closed 14

repo 1

  • datasette 14
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
273247186 MDU6SXNzdWUyNzMyNDcxODY= 68 Support for title/source/license metadata simonw 9599 closed 0   Ship first public release 2857392 4 2017-11-12T17:04:21Z 2017-12-04T04:55:43Z 2017-11-13T15:26:11Z OWNER  

I've decided this is important for launch: I want to set a precedent for people citing, licensing and documenting their datasets.

Not sure how best to go about supporting this. I'd like to allow for the following data to be optionally attached to any given database:

  • Title
  • Description, potentially in markdown?
  • Original source URL
  • License

I'd also like the ability to attach descriptions to individual tables - and maybe even to table columns?

The question then becomes: how should this information be stored. A few options:

  • In the SQLite database itself, in a specially named table. Problem here is that this means having to modify SQLite databases before publishing them.
  • In a separate SQLite database that can be published alongside the databases we are publishing.
  • In a JSON file. This is neat, but JSON files are not a great editing experience once you start including multiple lines (e.g. a markdown description).
  • In a YAML file. This is a better format for multi-line descriptions, but still isn't a great editing experience.

Whatever the format, it can be made much more usable by offering a web-based editing UI for populating it (a special mode the server can be run in).

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/68/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273569477 MDU6SXNzdWUyNzM1Njk0Nzc= 80 Deploy final versions of fivethirtyeight and parlgov datasets (with view pagination) simonw 9599 closed 0   Ship first public release 2857392 2 2017-11-13T20:37:46Z 2017-11-13T22:09:46Z 2017-11-13T22:09:46Z OWNER  

Final versions should be deployed using the first released version of datasette.

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/80/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273537940 MDU6SXNzdWUyNzM1Mzc5NDA= 77 Add Travis CI badge to README simonw 9599 closed 0   Ship first public release 2857392 0 2017-11-13T18:52:25Z 2017-11-13T21:24:15Z 2017-11-13T21:24:15Z OWNER  

Also fix this newline issue:

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/77/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273127117 MDU6SXNzdWUyNzMxMjcxMTc= 55 Ship first version to PyPI simonw 9599 closed 0   Ship first public release 2857392 2 2017-11-11T07:38:48Z 2017-11-13T21:19:43Z 2017-11-13T21:19:43Z OWNER  

Just before doing this, update the Dockerfile template to pip install datasette https://github.com/simonw/datasette/blob/65e350ca2a4845c25752a62c16ba58cfe2c14b9b/datasette/utils.py#L125

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/55/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273267081 MDU6SXNzdWUyNzMyNjcwODE= 70 Paginate views using OFFSET/LIMIT simonw 9599 closed 0   Ship first public release 2857392 0 2017-11-12T21:30:29Z 2017-11-13T21:11:01Z 2017-11-13T21:11:01Z OWNER  

As with #69 these should obey a maximum offset setting, which can be over-ridden.

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/70/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273554949 MDU6SXNzdWUyNzM1NTQ5NDk= 78 Rename after to next and provide a next_url simonw 9599 closed 0   Ship first public release 2857392 0 2017-11-13T19:48:31Z 2017-11-13T20:35:03Z 2017-11-13T20:35:03Z OWNER  
datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/78/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273248366 MDU6SXNzdWUyNzMyNDgzNjY= 69 Enforce pagination (or at least limits) for arbitrary custom SQL simonw 9599 closed 0   Ship first public release 2857392 4 2017-11-12T17:21:33Z 2017-11-13T20:32:47Z 2017-11-13T19:35:47Z OWNER  

It's way too easy to accidentally trigger a page that returns 100,000 rows at the moment. I need to use the LIMIT clause on views and custom SQL - I can support pagination "next" links using offset as well.

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/69/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273296684 MDU6SXNzdWUyNzMyOTY2ODQ= 74 Send a 302 redirect to the new hash for hits to old hashes simonw 9599 closed 0   Ship first public release 2857392 1 2017-11-13T03:00:59Z 2017-11-13T18:49:59Z 2017-11-13T18:49:59Z OWNER  
datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/74/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
272735257 MDU6SXNzdWUyNzI3MzUyNTc= 51 Make a proper README simonw 9599 closed 0   Ship first public release 2857392 1 2017-11-09T21:46:07Z 2017-11-13T18:44:23Z 2017-11-13T18:44:23Z OWNER  

Include instructions on building a local Docker container - currently detailed here: https://gist.github.com/simonw/0ea5c960608c2d876e4637a5e48aa95d (those instructions don't work now that we have removed the Dockerfile in favour of a template generated by datasette publish)

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/51/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273510781 MDU6SXNzdWUyNzM1MTA3ODE= 76 publish should have required argument specifying publisher simonw 9599 closed 0   Ship first public release 2857392 0 2017-11-13T17:21:26Z 2017-11-13T18:41:01Z 2017-11-13T18:41:01Z OWNER  

Initially the only argument will be “now” - but “hyper” can be added in the future

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/76/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273509159 MDU6SXNzdWUyNzM1MDkxNTk= 75 Add --cors argument to serve simonw 9599 closed 0   Ship first public release 2857392 1 2017-11-13T17:16:19Z 2017-11-13T18:17:52Z 2017-11-13T18:17:52Z OWNER  
datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/75/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273192789 MDU6SXNzdWUyNzMxOTI3ODk= 67 Command that builds a local docker container simonw 9599 closed 0   Ship first public release 2857392 2 2017-11-12T02:13:29Z 2017-11-13T16:17:52Z 2017-11-13T16:17:52Z OWNER  

Be nice to indicate that this isn't just for Now. Shouldn't be too hard either.

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/67/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273283166 MDU6SXNzdWUyNzMyODMxNjY= 72 publish command should take an optional --name argument simonw 9599 closed 0   Ship first public release 2857392 0 2017-11-13T00:59:35Z 2017-11-13T02:12:27Z 2017-11-13T02:12:27Z OWNER  

To set the directory name so that now will inherit it as the name of the app.

Defaults to datasette

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/72/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
273278840 MDU6SXNzdWUyNzMyNzg4NDA= 71 Set up some example datasets on a Cloudflare-backed domain simonw 9599 closed 0   Ship first public release 2857392 10 2017-11-13T00:06:30Z 2017-11-13T02:09:34Z 2017-11-13T02:09:34Z OWNER  

To better demonstrate the caching and HTTP/2 features, I'd like to go live with some demos that are hosted behind Cloudflare.

  • [x] Redirect https://datasettes.com/ and https://www.datasettes.com/ to https://github.com/simonw/datasette
  • [x] Have now domain add -e datasettes.com run without errors (hopefully just a matter of waiting for the DNS to update)
  • [x] Alias an example dataset hosted on Now on a datasettes.com subdomain
  • [x] Confirm that HTTP caching and HTTP/2 redirect pushing works as expected - this may require another page rule
datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/71/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]);
Powered by Datasette · Queries took 360.366ms · About: github-to-sqlite
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows