issue_comments

Table actions

1 row where issue = 1377811868 and user = 883348 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • adipasquale · 1 ✖

issue 1

  • missing next and next_url in JSON responses from an instance deployed on Fly · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1250901367 https://github.com/simonw/datasette/issues/1813#issuecomment-1250901367 https://api.github.com/repos/simonw/datasette/issues/1813 IC_kwDOBm6k_c5Kjz13 adipasquale 883348 2022-09-19T11:34:45Z 2022-09-19T11:34:45Z CONTRIBUTOR

oh and by writing this I just realized the difference: the URL on fly.io is with a custom SQL command whereas the local one is without. It seems that there is no pagination when using custom SQL commands which makes sense

Sorry for this useless issue, maybe this can be useful for someone else / me in the future.

Thanks again for this wonderful project !

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 missing next and next_url in JSON responses from an instance deployed on Fly  1377811868  

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