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/203#issuecomment-380951815 | https://api.github.com/repos/simonw/datasette/issues/203 | 380951815 | MDEyOklzc3VlQ29tbWVudDM4MDk1MTgxNQ== | 9599 | 2018-04-12T21:36:10Z | 2018-04-12T21:36:10Z | OWNER | I like this. I'd like to be able to attach a full description to a column as well. We could support these in `metadata.json` | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
313837303 | |
https://github.com/simonw/datasette/issues/203#issuecomment-380951920 | https://api.github.com/repos/simonw/datasette/issues/203 | 380951920 | MDEyOklzc3VlQ29tbWVudDM4MDk1MTkyMA== | 9599 | 2018-04-12T21:36:38Z | 2018-04-12T21:36:38Z | OWNER | This also feeds into the visualization features I want to add - we could use this kind of metadata to automatically apply meaningful labels to graphs. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
313837303 | |
https://github.com/simonw/datasette/issues/203#issuecomment-381300336 | https://api.github.com/repos/simonw/datasette/issues/203 | 381300336 | MDEyOklzc3VlQ29tbWVudDM4MTMwMDMzNg== | 9599 | 2018-04-14T03:35:02Z | 2018-04-14T03:35:02Z | OWNER | This is really cool - I'm very impressed by pint. I'd like to figure out a sensible opt-in way to expose this in the JSON output as well. Maybe with a `&_units=true` parameter? We should definitely expose the units section from the table metadata in the output of https://wtr-api.herokuapp.com/wtr-663ea99/license_frequency.json | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
313837303 | |
https://github.com/simonw/datasette/issues/203#issuecomment-381300386 | https://api.github.com/repos/simonw/datasette/issues/203 | 381300386 | MDEyOklzc3VlQ29tbWVudDM4MTMwMDM4Ng== | 9599 | 2018-04-14T03:35:56Z | 2018-04-14T03:35:56Z | OWNER | In #204 you said "I'd like to add support for using units when querying but this is PR is pretty usable as-is." - I'm fascinated to hear more about how this could work. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
313837303 | |
https://github.com/simonw/datasette/issues/203#issuecomment-381330075 | https://api.github.com/repos/simonw/datasette/issues/203 | 381330075 | MDEyOklzc3VlQ29tbWVudDM4MTMzMDA3NQ== | 9599 | 2018-04-14T13:41:53Z | 2018-04-14T13:41:53Z | OWNER | Presumably units only work for numeric fields? If that's the case then automatically processing them if the incoming query string argument has a unit suffix makes total sense to me. Here's a pretty crazy idea: what if we exposed unit conversion to SQL as a custom SQLite function? That way it would be possible to optionally use units in actual custom SQL queries. I'd have to think quite carefully about performance implications here - wouldn't want a poorly considered unit calculation over a 500,000 row table to lock up the server. But I think the 1s query time limit might still prevent that. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
313837303 | |
https://github.com/simonw/datasette/issues/203#issuecomment-381348849 | https://api.github.com/repos/simonw/datasette/issues/203 | 381348849 | MDEyOklzc3VlQ29tbWVudDM4MTM0ODg0OQ== | 9599 | 2018-04-14T18:12:52Z | 2018-04-14T18:12:52Z | OWNER | I think I'm going to hold on to the custom sql function idea for the moment and implement it as an example plugin. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
313837303 | |
https://github.com/simonw/datasette/issues/203#issuecomment-381446554 | https://api.github.com/repos/simonw/datasette/issues/203 | 381446554 | MDEyOklzc3VlQ29tbWVudDM4MTQ0NjU1NA== | 9599 | 2018-04-15T23:25:54Z | 2018-04-15T23:26:03Z | OWNER | I built a prototype of the `convert_units()` custom SQL function as a plugin over in https://github.com/simonw/datasette/issues/14#issuecomment-381446511 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
313837303 |