issue_comments
19 rows where author_association = "OWNER" and "updated_at" is on date 2020-10-19 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date)
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
712483066 | https://github.com/simonw/datasette/issues/904#issuecomment-712483066 | https://api.github.com/repos/simonw/datasette/issues/904 | MDEyOklzc3VlQ29tbWVudDcxMjQ4MzA2Ng== | simonw 9599 | 2020-10-19T22:46:48Z | 2020-10-19T22:46:48Z | OWNER | OK, I'm committing to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
datasette.urls.table() / .instance() / .database() methods for constructing URLs, also exposed to templates 663228985 | |
712482504 | https://github.com/simonw/datasette/issues/1020#issuecomment-712482504 | https://api.github.com/repos/simonw/datasette/issues/1020 | MDEyOklzc3VlQ29tbWVudDcxMjQ4MjUwNA== | simonw 9599 | 2020-10-19T22:45:01Z | 2020-10-19T22:45:01Z | OWNER | I'm having trouble coming up with the syntax for this. Here's one option:
We're essentially combining that request with the other arguments passed to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Method for datasette.client() to forward on authentication 721068929 | |
712482015 | https://github.com/simonw/datasette/issues/1020#issuecomment-712482015 | https://api.github.com/repos/simonw/datasette/issues/1020 | MDEyOklzc3VlQ29tbWVudDcxMjQ4MjAxNQ== | simonw 9599 | 2020-10-19T22:43:24Z | 2020-10-19T22:43:24Z | OWNER | ... unless I want to support authentication mechanisms that work based on incoming IP address instead, in which case there's an argument for copying more over from the incoming request. Tailscale is a good example of a system where authentication based on IP address can actually work well, so this is worth doing. Also, there might be authentication mechanisms which work by setting a custom header on the incoming request (not to mention the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Method for datasette.client() to forward on authentication 721068929 | |
712481568 | https://github.com/simonw/datasette/issues/1020#issuecomment-712481568 | https://api.github.com/repos/simonw/datasette/issues/1020 | MDEyOklzc3VlQ29tbWVudDcxMjQ4MTU2OA== | simonw 9599 | 2020-10-19T22:41:59Z | 2020-10-19T22:41:59Z | OWNER | It turns out this works just fine:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Method for datasette.client() to forward on authentication 721068929 | |
712480866 | https://github.com/simonw/datasette/issues/1028#issuecomment-712480866 | https://api.github.com/repos/simonw/datasette/issues/1028 | MDEyOklzc3VlQ29tbWVudDcxMjQ4MDg2Ng== | simonw 9599 | 2020-10-19T22:39:51Z | 2020-10-19T22:39:51Z | OWNER | Documentation: https://docs.datasette.io/en/latest/spatialite.html |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--load-extension=spatialite shortcut 723803777 | |
712367285 | https://github.com/simonw/datasette/issues/1032#issuecomment-712367285 | https://api.github.com/repos/simonw/datasette/issues/1032 | MDEyOklzc3VlQ29tbWVudDcxMjM2NzI4NQ== | simonw 9599 | 2020-10-19T18:39:32Z | 2020-10-19T18:39:32Z | OWNER | https://github.com/digital-land/brownfield-land-collection/blob/a09ddf9960a6af59e72dc02448f7b645e59bf227/bin/harmonise.py#L217-L247 is a beautiful example of this problem. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bring date parsing into Datasette core 724878151 | |
712365439 | https://github.com/simonw/datasette/issues/1032#issuecomment-712365439 | https://api.github.com/repos/simonw/datasette/issues/1032 | MDEyOklzc3VlQ29tbWVudDcxMjM2NTQzOQ== | simonw 9599 | 2020-10-19T18:35:50Z | 2020-10-19T18:37:57Z | OWNER | Maybe I don't need to add
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bring date parsing into Datasette core 724878151 | |
712365236 | https://github.com/simonw/datasette/issues/1032#issuecomment-712365236 | https://api.github.com/repos/simonw/datasette/issues/1032 | MDEyOklzc3VlQ29tbWVudDcxMjM2NTIzNg== | simonw 9599 | 2020-10-19T18:35:25Z | 2020-10-19T18:35:25Z | OWNER | Since I'm dealing with tables of data I usually have a whole column of examples, so heuristics that check for numbers-greater-than-12 could actually work well for many cases. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bring date parsing into Datasette core 724878151 | |
712364532 | https://github.com/simonw/datasette/issues/1032#issuecomment-712364532 | https://api.github.com/repos/simonw/datasette/issues/1032 | MDEyOklzc3VlQ29tbWVudDcxMjM2NDUzMg== | simonw 9599 | 2020-10-19T18:34:10Z | 2020-10-19T18:34:10Z | OWNER | Lots of great example date data in https://biglocal.datasettes.com/COVID_WARN_Notices |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bring date parsing into Datasette core 724878151 | |
712364317 | https://github.com/simonw/datasette/issues/1032#issuecomment-712364317 | https://api.github.com/repos/simonw/datasette/issues/1032 | MDEyOklzc3VlQ29tbWVudDcxMjM2NDMxNw== | simonw 9599 | 2020-10-19T18:33:42Z | 2020-10-19T18:33:42Z | OWNER | Related challenge: timezones. I think I'll punt on those for the moment and just concentrate on dates, but I should keep them in mind. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bring date parsing into Datasette core 724878151 | |
712363825 | https://github.com/simonw/datasette/issues/1032#issuecomment-712363825 | https://api.github.com/repos/simonw/datasette/issues/1032 | MDEyOklzc3VlQ29tbWVudDcxMjM2MzgyNQ== | simonw 9599 | 2020-10-19T18:32:43Z | 2020-10-19T18:32:43Z | OWNER | Horrible thought: I bet there is data out there that uses more than one date format in the same table! So this needs to be exposed as a visible per-column setting. Column action menu can help here, although it's not yet the full solution because it isn't yet visible on mobile. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bring date parsing into Datasette core 724878151 | |
712363344 | https://github.com/simonw/datasette/issues/1032#issuecomment-712363344 | https://api.github.com/repos/simonw/datasette/issues/1032 | MDEyOklzc3VlQ29tbWVudDcxMjM2MzM0NA== | simonw 9599 | 2020-10-19T18:31:46Z | 2020-10-19T18:31:46Z | OWNER | As always with dates, the challenge is America. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bring date parsing into Datasette core 724878151 | |
712355877 | https://github.com/simonw/datasette/issues/904#issuecomment-712355877 | https://api.github.com/repos/simonw/datasette/issues/904 | MDEyOklzc3VlQ29tbWVudDcxMjM1NTg3Nw== | simonw 9599 | 2020-10-19T18:17:22Z | 2020-10-19T18:17:22Z | OWNER | I quite like |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
datasette.urls.table() / .instance() / .database() methods for constructing URLs, also exposed to templates 663228985 | |
712355706 | https://github.com/simonw/datasette/issues/904#issuecomment-712355706 | https://api.github.com/repos/simonw/datasette/issues/904 | MDEyOklzc3VlQ29tbWVudDcxMjM1NTcwNg== | simonw 9599 | 2020-10-19T18:17:03Z | 2020-10-19T18:17:03Z | OWNER | Options:
- |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
datasette.urls.table() / .instance() / .database() methods for constructing URLs, also exposed to templates 663228985 | |
712354600 | https://github.com/simonw/datasette/issues/904#issuecomment-712354600 | https://api.github.com/repos/simonw/datasette/issues/904 | MDEyOklzc3VlQ29tbWVudDcxMjM1NDYwMA== | simonw 9599 | 2020-10-19T18:15:03Z | 2020-10-19T18:15:39Z | OWNER | Related: #1026 (How should datasette.client interact with base_url) Also this comment from https://github.com/simonw/datasette/issues/943#issuecomment-675752436
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
datasette.urls.table() / .instance() / .database() methods for constructing URLs, also exposed to templates 663228985 | |
712324077 | https://github.com/simonw/datasette/issues/904#issuecomment-712324077 | https://api.github.com/repos/simonw/datasette/issues/904 | MDEyOklzc3VlQ29tbWVudDcxMjMyNDA3Nw== | simonw 9599 | 2020-10-19T17:39:38Z | 2020-10-19T17:39:38Z | OWNER | If I do these methods I think this should be available on the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
datasette.urls.table() / .instance() / .database() methods for constructing URLs, also exposed to templates 663228985 | |
710487083 | https://github.com/simonw/datasette/issues/904#issuecomment-710487083 | https://api.github.com/repos/simonw/datasette/issues/904 | MDEyOklzc3VlQ29tbWVudDcxMDQ4NzA4Mw== | simonw 9599 | 2020-10-16T19:34:10Z | 2020-10-19T17:39:04Z | OWNER | Alternatively, I could expose a single object that knows how to construct all kinds of URLs. Something like this:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
datasette.urls.table() / .instance() / .database() methods for constructing URLs, also exposed to templates 663228985 | |
712320103 | https://github.com/simonw/datasette/issues/1027#issuecomment-712320103 | https://api.github.com/repos/simonw/datasette/issues/1027 | MDEyOklzc3VlQ29tbWVudDcxMjMyMDEwMw== | simonw 9599 | 2020-10-19T17:35:04Z | 2020-10-19T17:35:04Z | OWNER | Still need to configure proxying though. https://www.netnea.com/cms/apache-tutorial-9_setting-up-a-reverse-proxy/ |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add documentation on serving Datasette behind a proxy using base_url 722758132 | |
712317638 | https://github.com/simonw/datasette/issues/991#issuecomment-712317638 | https://api.github.com/repos/simonw/datasette/issues/991 | MDEyOklzc3VlQ29tbWVudDcxMjMxNzYzOA== | simonw 9599 | 2020-10-19T17:30:56Z | 2020-10-19T17:30:56Z | OWNER | https://biglocal.datasettes.com/ is one of my larger Datasettes in terms of number of databases. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Redesign application homepage 714377268 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [issue] INTEGER REFERENCES [issues]([id]) , [performed_via_github_app] TEXT); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
issue 6