issue_comments

Table actions

3 rows where author_association = "OWNER", "created_at" is on date 2022-03-19 and issue = 1174302994 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

issue 1

  • Make route matched pattern groups more consistent · 3 ✖

author_association 1

  • OWNER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1073076624 https://github.com/simonw/datasette/issues/1667#issuecomment-1073076624 https://api.github.com/repos/simonw/datasette/issues/1667 IC_kwDOBm6k_c4_9dmQ simonw 9599 2022-03-19T20:31:44Z 2022-03-19T20:31:44Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Make route matched pattern groups more consistent 1174302994  
1073042554 https://github.com/simonw/datasette/issues/1667#issuecomment-1073042554 https://api.github.com/repos/simonw/datasette/issues/1667 IC_kwDOBm6k_c4_9VR6 simonw 9599 2022-03-19T16:50:01Z 2022-03-19T16:52:35Z OWNER

OK, I've made this more consistent - I still need to address the fact that format can be .json or json or not used at all before I close this issue.

https://github.com/simonw/datasette/blob/61419388c134001118aaf7dfb913562d467d7913/tests/test_routes.py#L15-L35

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Make route matched pattern groups more consistent 1174302994  
1073040072 https://github.com/simonw/datasette/issues/1667#issuecomment-1073040072 https://api.github.com/repos/simonw/datasette/issues/1667 IC_kwDOBm6k_c4_9UrI simonw 9599 2022-03-19T16:34:02Z 2022-03-19T16:34:02Z OWNER

I called it as_format to avoid clashing with the Python built-in format() function when these things were turned into keyword arguments, but now that they're not I can use format instead.

I think I'm going to go with database, table, format and pks.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Make route matched pattern groups more consistent 1174302994  

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