issue_comments

Table actions

3 rows where user = 247131 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: issue_url, created_at (date), updated_at (date)

user 1

  • philroche · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
626340387 https://github.com/simonw/datasette/issues/254#issuecomment-626340387 https://api.github.com/repos/simonw/datasette/issues/254 MDEyOklzc3VlQ29tbWVudDYyNjM0MDM4Nw== philroche 247131 2020-05-10T14:54:13Z 2020-05-10T14:54:13Z NONE

This has now been resolved and is not present in current version of datasette.

Sample query @simonw mentioned now returns as expected.

https://aggreg8streams.tinyviking.ie/simplestreams?sql=select+*+from+cloudimage+where+%22content_id%22+%3D+%22com.ubuntu.cloud%3Areleased%3Adownload%22+order+by+id+limit+10

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Escaping named parameters in canned queries 322283067  
390577711 https://github.com/simonw/datasette/pull/258#issuecomment-390577711 https://api.github.com/repos/simonw/datasette/issues/258 MDEyOklzc3VlQ29tbWVudDM5MDU3NzcxMQ== philroche 247131 2018-05-21T07:38:15Z 2018-05-21T07:38:15Z NONE

Excellent, I was not aware of the auto redirect to the new hash. My bad

This solves my use case.

I do agree that your suggested --no-url-hash approach is much neater. I will investigate 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add new metadata key persistent_urls which removes the hash from all database urls 322741659  
388367027 https://github.com/simonw/datasette/issues/254#issuecomment-388367027 https://api.github.com/repos/simonw/datasette/issues/254 MDEyOklzc3VlQ29tbWVudDM4ODM2NzAyNw== philroche 247131 2018-05-11T13:41:46Z 2018-05-11T13:41:46Z NONE

An example deployment @ https://datasette-zkcvlwdrhl.now.sh/simplestreams-270f20c/cloudimage?content_id__exact=com.ubuntu.cloud%3Areleased%3Adownload

It is not causing errors, more of an inconvenience. I have worked around it using a like query instead. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Escaping named parameters in canned queries 322283067  

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