issue_comments

Table actions

1 row where issue = 192248351 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • max-sixty · 1 ✖

issue 1

  • win_type for rolling() ? · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
263678778 https://github.com/pydata/xarray/issues/1142#issuecomment-263678778 https://api.github.com/repos/pydata/xarray/issues/1142 MDEyOklzc3VlQ29tbWVudDI2MzY3ODc3OA== max-sixty 5635139 2016-11-29T19:50:08Z 2016-11-29T19:50:08Z MEMBER

Think it would be useful generally. @jhamman will have a better view of how difficult it is to implement. Our use cases are fine with simple windows, although an ewm object would be helpful.

One API choice is to what extent we want .rolling, .expanding & .ewm to be separate objects vs kwargs to .rolling

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   win_type for rolling() ? 192248351

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,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);