issue_comments

Table actions

1 row where author_association = "NONE", issue = 417412201 and user = 601177 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

  • equaeghe · 1 ✖

issue 1

  • stack renames single dimensions instead of creating a MultiIndex · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
469885042 https://github.com/pydata/xarray/issues/2802#issuecomment-469885042 https://api.github.com/repos/pydata/xarray/issues/2802 MDEyOklzc3VlQ29tbWVudDQ2OTg4NTA0Mg== equaeghe 601177 2019-03-05T22:31:44Z 2019-03-05T22:31:44Z NONE

Is this a dupe of #1431 ?

Yes. My example and explanation are a bit clearer, so I do not know which would be best to close.

In any case, I hope this is considered for fixing separately from some big refactoring of the MultiIndex machinery, which seems to have stalled. This seems like a corner case that might not be too big, but I may be mistaken.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   stack renames single dimensions instead of creating a MultiIndex 417412201

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