github
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/simonw/datasette/issues/1050#issuecomment-719021514 | https://api.github.com/repos/simonw/datasette/issues/1050 | 719021514 | MDEyOklzc3VlQ29tbWVudDcxOTAyMTUxNA== | 9599 | 2020-10-29T21:05:08Z | 2020-10-29T21:05:08Z | OWNER | Idea: what if Datasette had a custom SQLite function that could be used to generate URLs to the row-level BLOB download for a value? Then custom SQL query authors could use that function to link to the relevant content. This could be expanded to exposing other `datasette.urls` functionality as well. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
729057388 | |
https://github.com/simonw/datasette/issues/1050#issuecomment-719001701 | https://api.github.com/repos/simonw/datasette/issues/1050 | 719001701 | MDEyOklzc3VlQ29tbWVudDcxOTAwMTcwMQ== | 9599 | 2020-10-29T20:26:44Z | 2020-10-29T20:26:44Z | OWNER | I'll do the rest of the work on this in the pull request #1061. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
729057388 | |
https://github.com/simonw/datasette/issues/1050#issuecomment-718989895 | https://api.github.com/repos/simonw/datasette/issues/1050 | 718989895 | MDEyOklzc3VlQ29tbWVudDcxODk4OTg5NQ== | 9599 | 2020-10-29T20:04:15Z | 2020-10-29T20:04:15Z | OWNER | I'll use `hashlib.sha256` for these hashes. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
729057388 | |
https://github.com/simonw/datasette/issues/1050#issuecomment-718987852 | https://api.github.com/repos/simonw/datasette/issues/1050 | 718987852 | MDEyOklzc3VlQ29tbWVudDcxODk4Nzg1Mg== | 9599 | 2020-10-29T20:00:32Z | 2020-10-29T20:00:32Z | OWNER | The reason I like the `?_blob_hash=` solution is that it feels really misleading to provide a link to "download this binary" which could conceivably download some other data. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
729057388 | |
https://github.com/simonw/datasette/issues/1050#issuecomment-718980944 | https://api.github.com/repos/simonw/datasette/issues/1050 | 718980944 | MDEyOklzc3VlQ29tbWVudDcxODk4MDk0NA== | 9599 | 2020-10-29T19:46:19Z | 2020-10-29T19:46:19Z | OWNER | Had an idea in https://github.com/simonw/datasette/issues/1051#issuecomment-718980659 > OK, alternative idea. The `.blob` output renderer from #1050 gets to see multiple rows at once. > > For an arbitrary SQL query, how about if I link to this? > > `/db.blob?sql=...&_blob_column=data&_blob_hash=bc4c24181ed3ce666` > > Then the output renderer loops through all of the `data` results that are available to it and, if one of them hashes to that value, serves up that data? > > If no matches are found it can show an error message telling you that the link has expired (presumably because the underlying database has changed since the link was generated). > > I think this might be the best solution to the problem. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
729057388 | |
https://github.com/simonw/datasette/issues/1050#issuecomment-718346019 | https://api.github.com/repos/simonw/datasette/issues/1050 | 718346019 | MDEyOklzc3VlQ29tbWVudDcxODM0NjAxOQ== | 9599 | 2020-10-29T04:05:07Z | 2020-10-29T04:05:07Z | OWNER | Yes, confirmed - this is a bug where if the `BLOB` column contains a `null` you get a nasty exception if you try to download it. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
729057388 |