issue_comments
13 rows where "created_at" is on date 2018-04-08, reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw · 13 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
379592393 | https://github.com/simonw/datasette/issues/189#issuecomment-379592393 | https://api.github.com/repos/simonw/datasette/issues/189 | MDEyOklzc3VlQ29tbWVudDM3OTU5MjM5Mw== | simonw 9599 | 2018-04-08T23:45:42Z | 2018-04-08T23:46:31Z | OWNER | Actually next page SQL when sorting looks more like this:
The next page after row 190 with sortable value 111 should show either records that are greater than 111 or records that match 111 but have a greater primary key than the last one seen. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to sort (and paginate) by column 309471814 | |
379591062 | https://github.com/simonw/datasette/issues/189#issuecomment-379591062 | https://api.github.com/repos/simonw/datasette/issues/189 | MDEyOklzc3VlQ29tbWVudDM3OTU5MTA2Mg== | simonw 9599 | 2018-04-08T23:23:12Z | 2018-04-08T23:23:12Z | OWNER | To break this up into smaller units, the first implementation of this will only support a single |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to sort (and paginate) by column 309471814 | |
379588602 | https://github.com/simonw/datasette/issues/195#issuecomment-379588602 | https://api.github.com/repos/simonw/datasette/issues/195 | MDEyOklzc3VlQ29tbWVudDM3OTU4ODYwMg== | simonw 9599 | 2018-04-08T22:40:16Z | 2018-04-08T22:40:16Z | OWNER | Could also identify all views for that database, which would save on these queries: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Run pks_for_table in inspect, executing once at build time rather than constantly 312313496 | |
379559319 | https://github.com/simonw/datasette/issues/150#issuecomment-379559319 | https://api.github.com/repos/simonw/datasette/issues/150 | MDEyOklzc3VlQ29tbWVudDM3OTU1OTMxOQ== | simonw 9599 | 2018-04-08T15:35:43Z | 2018-04-08T15:35:43Z | OWNER | From a code point of view, the current mechanism for Instead, I think if |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
_group_count= feature improvements 276704327 | |
379559214 | https://github.com/simonw/datasette/issues/150#issuecomment-379559214 | https://api.github.com/repos/simonw/datasette/issues/150 | MDEyOklzc3VlQ29tbWVudDM3OTU1OTIxNA== | simonw 9599 | 2018-04-08T15:33:58Z | 2018-04-08T15:33:58Z | OWNER | The single biggest challenge here is expanding foreign key references. This is the blocker that prevents |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
_group_count= feature improvements 276704327 | |
379559074 | https://github.com/simonw/datasette/issues/195#issuecomment-379559074 | https://api.github.com/repos/simonw/datasette/issues/195 | MDEyOklzc3VlQ29tbWVudDM3OTU1OTA3NA== | simonw 9599 | 2018-04-08T15:31:49Z | 2018-04-08T15:31:49Z | OWNER | While I'm at it, doing the same thing for fts_table detection is worth considering: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Run pks_for_table in inspect, executing once at build time rather than constantly 312313496 | |
379557982 | https://github.com/simonw/datasette/issues/189#issuecomment-379557982 | https://api.github.com/repos/simonw/datasette/issues/189 | MDEyOklzc3VlQ29tbWVudDM3OTU1Nzk4Mg== | simonw 9599 | 2018-04-08T15:16:49Z | 2018-04-08T15:16:49Z | OWNER | A note about views: a view cannot be paginated using keyset pagination because records returned from a view don't have a primary key - so there's no way to reliably distinguish between _next= records when the sorted column has duplicates with the same value. Datasette already takes this into account: views are paginated using offset/limit instead. We can continue to do that even for views that have been sorted using a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to sort (and paginate) by column 309471814 | |
379557743 | https://github.com/simonw/datasette/issues/195#issuecomment-379557743 | https://api.github.com/repos/simonw/datasette/issues/195 | MDEyOklzc3VlQ29tbWVudDM3OTU1Nzc0Mw== | simonw 9599 | 2018-04-08T15:13:18Z | 2018-04-08T15:13:18Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Run pks_for_table in inspect, executing once at build time rather than constantly 312313496 | ||
379556881 | https://github.com/simonw/datasette/issues/194#issuecomment-379556881 | https://api.github.com/repos/simonw/datasette/issues/194 | MDEyOklzc3VlQ29tbWVudDM3OTU1Njg4MQ== | simonw 9599 | 2018-04-08T15:00:48Z | 2018-04-08T15:02:35Z | OWNER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename table_rows and filtered_table_rows to have _count suffix 312312125 | |
379556981 | https://github.com/simonw/datasette/issues/194#issuecomment-379556981 | https://api.github.com/repos/simonw/datasette/issues/194 | MDEyOklzc3VlQ29tbWVudDM3OTU1Njk4MQ== | simonw 9599 | 2018-04-08T15:02:23Z | 2018-04-08T15:02:23Z | OWNER | Maybe |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename table_rows and filtered_table_rows to have _count suffix 312312125 | |
379556774 | https://github.com/simonw/datasette/issues/189#issuecomment-379556774 | https://api.github.com/repos/simonw/datasette/issues/189 | MDEyOklzc3VlQ29tbWVudDM3OTU1Njc3NA== | simonw 9599 | 2018-04-08T14:59:05Z | 2018-04-08T14:59:05Z | OWNER | A common problem with keyset pagination is that it can distort the "total number of rows" logic - every time you navigate to a further page the total rows count can decrease due to the extra arguments in the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to sort (and paginate) by column 309471814 | |
379556637 | https://github.com/simonw/datasette/issues/48#issuecomment-379556637 | https://api.github.com/repos/simonw/datasette/issues/48 | MDEyOklzc3VlQ29tbWVudDM3OTU1NjYzNw== | simonw 9599 | 2018-04-08T14:56:52Z | 2018-04-08T14:56:52Z | OWNER | It would be useful to have a microbenchmark in place to help understand how much of a performance benefit this would actually provide. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Switch to ujson 272391665 | |
379555484 | https://github.com/simonw/datasette/issues/189#issuecomment-379555484 | https://api.github.com/repos/simonw/datasette/issues/189 | MDEyOklzc3VlQ29tbWVudDM3OTU1NTQ4NA== | simonw 9599 | 2018-04-08T14:39:57Z | 2018-04-08T14:39:57Z | OWNER | I'm going to combine the code for explicit sorting with the existing code for _next= pagination - so even tables without an explicit sort order will run through the same code since they are ordered and paginated by primary key. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to sort (and paginate) by column 309471814 |
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 5