issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 441088452 and user = 5635139 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

  • max-sixty · 1 ✖

issue 1

  • `groupby` does not correctly handle non-dimensional coordinate · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
540209789 https://github.com/pydata/xarray/issues/2944#issuecomment-540209789 https://api.github.com/repos/pydata/xarray/issues/2944 MDEyOklzc3VlQ29tbWVudDU0MDIwOTc4OQ== max-sixty 5635139 2019-10-09T21:32:05Z 2019-10-09T21:32:05Z MEMBER

I had generally thought that we didn't want to keep non-dim coords along the group by i.e. if you want to keep them, put them as variables.

I'm also think it would be difficult to resolve issues like whether or not to keep coords based on their type in a way that wasn't surprising (though I guess we have to do it for data vars, even if we don't hit it often).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `groupby` does not correctly handle non-dimensional coordinate 441088452

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