issue_comments

Table actions

2 rows where author_association = "MEMBER" and issue = 237008177 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

  • groupby should still squeeze for non-monotonic inputs · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1059546596 https://github.com/pydata/xarray/issues/1460#issuecomment-1059546596 https://api.github.com/repos/pydata/xarray/issues/1460 IC_kwDOAMm_X84_J2Xk shoyer 1217238 2022-03-04T21:31:41Z 2022-03-04T21:31:41Z MEMBER

Well, even if we keep squeeze as an option, I think squeeze=False would be much more consistent default behavior :)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   groupby should still squeeze for non-monotonic inputs 237008177
766420609 https://github.com/pydata/xarray/issues/1460#issuecomment-766420609 https://api.github.com/repos/pydata/xarray/issues/1460 MDEyOklzc3VlQ29tbWVudDc2NjQyMDYwOQ== shoyer 1217238 2021-01-24T19:49:28Z 2021-01-24T19:49:28Z MEMBER

A better long term solution is probably removing "squeeze" from groupby entirely: https://github.com/pydata/xarray/issues/2157

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   groupby should still squeeze for non-monotonic inputs 237008177

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