issue_comments

Table actions

2 rows where author_association = "OWNER", issue = 1161937073 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • simonw · 2 ✖

issue 1

  • Mechanism to default a table to sorting by multiple columns · 2 ✖

author_association 1

  • OWNER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1061150672 https://github.com/simonw/datasette/issues/1653#issuecomment-1061150672 https://api.github.com/repos/simonw/datasette/issues/1653 IC_kwDOBm6k_c4_P9_Q simonw 9599 2022-03-07T21:23:39Z 2022-03-07T21:23:39Z OWNER

There may be a short-term fix for this: table view could start accepting a ?_sort_sql=SQLfragment parameter, similar to the ?_where= parameter described here: https://docs.datasette.io/en/stable/json_api.html#special-table-arguments

That fragment could then be pre-populated in metadata. Makes me think maybe that ?_where= should be optionally settable in metadata too?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Mechanism to default a table to sorting by multiple columns 1161937073  
1061148807 https://github.com/simonw/datasette/issues/1653#issuecomment-1061148807 https://api.github.com/repos/simonw/datasette/issues/1653 IC_kwDOBm6k_c4_P9iH simonw 9599 2022-03-07T21:21:23Z 2022-03-07T21:21:23Z OWNER

This is currently blocked on the fact that Datasette doesn't have a mechanism for sorting by more than one column: - #197

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Mechanism to default a table to sorting by multiple columns 1161937073  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);