html_url,issue_url,id,node_id,user,user_label,created_at,updated_at,author_association,body,reactions,issue,issue_label,performed_via_github_app
https://github.com/simonw/datasette/issues/4#issuecomment-338806718,https://api.github.com/repos/simonw/datasette/issues/4,338806718,MDEyOklzc3VlQ29tbWVudDMzODgwNjcxOA==,9599,simonw,2017-10-23T21:47:53Z,2017-10-23T21:47:53Z,OWNER,"Here's what the homepage of cloudflare.com does (with newlines added within the link header for clarity):

    $ curl -i 'https://www.cloudflare.com/' 
    HTTP/1.1 200 OK
    Date: Mon, 23 Oct 2017 21:45:58 GMT
    Content-Type: text/html; charset=utf-8
    Transfer-Encoding: chunked
    Connection: keep-alive
    link:
        </vendor/bitdashplayer.min.css>; rel=preload; as=style,
        </vendor/bitdash-controls.min.css>; rel=preload; as=style,
        </video/marketing-video/cloudflare-marketing-video.mpd>; rel=preload,
        </video/marketing-video/cloudflare-marketing-video.m3u8>; rel=preload,
        </video/marketing-video/video_0_800000/dash/init.mp4>; rel=preload; as=video,
        </video/marketing-video/audio_0_128000/dash/init.mp4>; rel=preload; as=video,
        </video/marketing-video/video_0_800000/dash/segment_0.m4s>; rel=preload; as=video,
        </video/marketing-video/audio_0_128000/dash/segment_0.m4s>; rel=preload; as=video,
        </video/new-short-optimized-22.mp4>; rel=preload; as=video,
        </video/marketing-video/poster.jpg>; rel=preload; as=image

The original header looked like this:

    link: </vendor/bitdashplayer.min.css>; rel=preload; as=style, </vendor/bitdash-controls.min.css>; rel=preload; as=style, </video/marketing-video/cloudflare-marketing-video.mpd>; rel=preload, </video/marketing-video/cloudflare-marketing-video.m3u8>; rel=preload, </video/marketing-video/video_0_800000/dash/init.mp4>; rel=preload; as=video, </video/marketing-video/audio_0_128000/dash/init.mp4>; rel=preload; as=video, </video/marketing-video/video_0_800000/dash/segment_0.m4s>; rel=preload; as=video, </video/marketing-video/audio_0_128000/dash/segment_0.m4s>; rel=preload; as=video, </video/new-short-optimized-22.mp4>; rel=preload; as=video, </video/marketing-video/poster.jpg>; rel=preload; as=image

","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267515836,Make URLs immutable,
https://github.com/simonw/datasette/issues/4#issuecomment-338804173,https://api.github.com/repos/simonw/datasette/issues/4,338804173,MDEyOklzc3VlQ29tbWVudDMzODgwNDE3Mw==,9599,simonw,2017-10-23T21:36:37Z,2017-10-23T21:36:37Z,OWNER,"Looks like the easiest way to implement HTTP/2 server push today is to run behind Cloudflare and use this:

    Link: </asset/to/push.js>; rel=preload; as=script

https://blog.cloudflare.com/announcing-support-for-http-2-server-push-2/

Here's the W3C draft: https://w3c.github.io/preload/

From https://w3c.github.io/preload/#as-attribute it looks like I should use `as=fetch` if the content is intended for consumption by fetch() or XMLHTTPRequest.

Unclear if I should throw `as=fetch crossorigin` in there. Need to experiment on that.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267515836,Make URLs immutable,
https://github.com/simonw/datasette/issues/4#issuecomment-338799438,https://api.github.com/repos/simonw/datasette/issues/4,338799438,MDEyOklzc3VlQ29tbWVudDMzODc5OTQzOA==,9599,simonw,2017-10-23T21:17:25Z,2017-10-23T21:17:25Z,OWNER,Can I take  advantage of HTTP/2 so even if you get redirected I start serving you the correct resource straight away?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267515836,Make URLs immutable,
https://github.com/simonw/datasette/issues/4#issuecomment-338797522,https://api.github.com/repos/simonw/datasette/issues/4,338797522,MDEyOklzc3VlQ29tbWVudDMzODc5NzUyMg==,9599,simonw,2017-10-23T21:09:33Z,2017-10-23T21:09:33Z,OWNER,"https://stackoverflow.com/a/18134919/6083 is a good answer about how many characters of the hash are needed to be unique. I say we default to 7 characters, like git does - but allow extras to be configured.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267515836,Make URLs immutable,
https://github.com/simonw/datasette/issues/4#issuecomment-338789734,https://api.github.com/repos/simonw/datasette/issues/4,338789734,MDEyOklzc3VlQ29tbWVudDMzODc4OTczNA==,9599,simonw,2017-10-23T20:40:25Z,2017-10-23T21:10:19Z,OWNER,"URL design:

     /database/table.json - redirects to /database-6753f4a/table.json

So we always redirect to the version with the truncated hash in the URL.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267515836,Make URLs immutable,
https://github.com/simonw/datasette/issues/20#issuecomment-338769538,https://api.github.com/repos/simonw/datasette/issues/20,338769538,MDEyOklzc3VlQ29tbWVudDMzODc2OTUzOA==,9599,simonw,2017-10-23T19:25:55Z,2017-10-23T19:25:55Z,OWNER,"Maybe this should be handled by views instead?

https://stateless-datasets-wreplxalgu.now.sh/ lists some views

https://stateless-datasets-wreplxalgu.now.sh/?sql=select%20*%20from%20%22Order%20Subtotals%22 is an example showing the content of a view.

What would the URL to views be? I don't think a view can share a name with a table, so the same URL scheme could work for both.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267759136,Config file with support for defining canned queries,
https://github.com/simonw/datasette/issues/16#issuecomment-338768860,https://api.github.com/repos/simonw/datasette/issues/16,338768860,MDEyOklzc3VlQ29tbWVudDMzODc2ODg2MA==,9599,simonw,2017-10-23T19:23:29Z,2017-10-23T19:23:29Z,OWNER,I could use the table-reflow mechanism demonstrated here: http://demos.jquerymobile.com/1.4.3/table-reflow/,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267726219,Default HTML/CSS needs to look reasonable and be responsive,
https://github.com/simonw/datasette/issues/8#issuecomment-338697223,https://api.github.com/repos/simonw/datasette/issues/8,338697223,MDEyOklzc3VlQ29tbWVudDMzODY5NzIyMw==,9599,simonw,2017-10-23T15:28:11Z,2017-10-23T15:28:11Z,OWNER,"Now returning this:

    {
        ""error"": ""attempt to write a readonly database"",
        ""ok"": false
    }
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267517314,Attempting an INSERT or UPDATE should return a sane error message,
https://github.com/simonw/datasette/issues/4#issuecomment-338531827,https://api.github.com/repos/simonw/datasette/issues/4,338531827,MDEyOklzc3VlQ29tbWVudDMzODUzMTgyNw==,9599,simonw,2017-10-23T02:28:31Z,2017-10-23T02:29:05Z,OWNER,"Many of the applications I want to implement with this would benefit from having permanent real URLs.

So let’s have both. The sha1 urls will serve far future cache headers (and an etag derived from their path). The non sha1 URLs will serve 302 uncached redirects to the sha1 locations.

We will have a setting that lets people opt out of this behavior.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267515836,Make URLs immutable,
https://github.com/simonw/datasette/issues/11#issuecomment-338530704,https://api.github.com/repos/simonw/datasette/issues/11,338530704,MDEyOklzc3VlQ29tbWVudDMzODUzMDcwNA==,9599,simonw,2017-10-23T02:18:36Z,2017-10-23T02:18:36Z,OWNER,Needed by https://github.com/simonw/stateless-datasets/issues/4#issuecomment-338530389,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267522549,Code that generates compile-time properties about the database ,
https://github.com/simonw/datasette/issues/4#issuecomment-338530480,https://api.github.com/repos/simonw/datasette/issues/4,338530480,MDEyOklzc3VlQ29tbWVudDMzODUzMDQ4MA==,9599,simonw,2017-10-23T02:16:33Z,2017-10-23T02:16:33Z,OWNER," How about when the service starts up it checks for a compile.json file and, if it is missing, creates it using the same code we run at compile time normally ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267515836,Make URLs immutable,
https://github.com/simonw/datasette/issues/4#issuecomment-338530389,https://api.github.com/repos/simonw/datasette/issues/4,338530389,MDEyOklzc3VlQ29tbWVudDMzODUzMDM4OQ==,9599,simonw,2017-10-23T02:15:41Z,2017-10-23T02:15:41Z,OWNER,"This means I need a good solution for these compile time options while running in development mode  
 ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267515836,Make URLs immutable,
https://github.com/simonw/datasette/issues/3#issuecomment-338526148,https://api.github.com/repos/simonw/datasette/issues/3,338526148,MDEyOklzc3VlQ29tbWVudDMzODUyNjE0OA==,9599,simonw,2017-10-23T01:35:17Z,2017-10-23T01:35:17Z,OWNER,https://github.com/ahupp/python-magic/blob/master/README.md,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267515678,"Make individual column valuables addressable, with smart content types",
https://github.com/simonw/datasette/issues/5#issuecomment-338524857,https://api.github.com/repos/simonw/datasette/issues/5,338524857,MDEyOklzc3VlQ29tbWVudDMzODUyNDg1Nw==,9599,simonw,2017-10-23T01:20:30Z,2017-10-23T01:20:30Z,OWNER,"https://stackoverflow.com/a/14468878/6083

Looks like I should order by compound primary key and implement cursor-based pagination.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267516066,Implement sensible query pagination,
https://github.com/simonw/datasette/issues/1#issuecomment-338524454,https://api.github.com/repos/simonw/datasette/issues/1,338524454,MDEyOklzc3VlQ29tbWVudDMzODUyNDQ1NA==,9599,simonw,2017-10-23T01:15:24Z,2017-10-23T01:15:24Z,OWNER,Table rendering logic needs to detect the primary key field and turn it into a hyperlink. If there is a compound primary key it should add an extra column at the start of the table which displays the compound key as a link,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267513424,Addressable pages for every row in a table,
https://github.com/simonw/datasette/issues/1#issuecomment-338523957,https://api.github.com/repos/simonw/datasette/issues/1,338523957,MDEyOklzc3VlQ29tbWVudDMzODUyMzk1Nw==,9599,simonw,2017-10-23T01:09:05Z,2017-10-24T02:42:12Z,OWNER,"I also need to solve for weird primary keys. If it’s a single integer or a single char field that’s easy. But what if it is a compound key with more than one chat field? What delimiter can I use that will definitely be safe?

Let’s say I use hyphen. Now I need to find a durable encoding for any hyphens that might exist in the key fields themselves.

How about I use URLencoding for every non-alpha-numeric character? That will turn hyphens into (I think) %2D. It should also solve for unicode characters, but it means the vast majority of keys (integers) will display neatly, including a compound key of eg 5678-345

","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",267513424,Addressable pages for every row in a table,