issue_comments

Table actions

1 row where issue = 370960004 and user = 1217238 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

  • shoyer · 1 ✖

issue 1

  • Renaming a coordinate of a multi-index after stack fails · 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
431097096 https://github.com/pydata/xarray/issues/2489#issuecomment-431097096 https://api.github.com/repos/pydata/xarray/issues/2489 MDEyOklzc3VlQ29tbWVudDQzMTA5NzA5Ng== shoyer 1217238 2018-10-18T17:35:46Z 2018-10-18T17:35:46Z MEMBER

MultiIndex levels should really be xarray.Variable objects, but unfortunately that isn't the case right now. We have some special cases in indexing to dynamically create xarray.Variable objects, but it isn't done consistently in all functions.

The refactor envisioned in https://github.com/pydata/xarray/issues/1603 should eventually fix this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Renaming a coordinate of a multi-index after stack fails 370960004

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