issue_comments

Table actions

1 row where issue = 692106936 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • keewis · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
739586590 https://github.com/pydata/xarray/issues/4404#issuecomment-739586590 https://api.github.com/repos/pydata/xarray/issues/4404 MDEyOklzc3VlQ29tbWVudDczOTU4NjU5MA== keewis 14808389 2020-12-06T23:44:48Z 2020-12-06T23:44:48Z MEMBER

thanks for the detailed analysis, @kmpaul, and I'm sorry for the late reply.

The reason why we have the special treatment for tuple data seems to be that we need that for MultiIndex support (at least, removing it fails mostly tests related to MultiIndex). I agree that the error message is not helpful, and we could definitely do better with the documentation.

Since detecting this to make the error message more helpful seems pretty difficult (at the point where the coords and data are compared we can't determine whether a tuple or a 0d object array were passed) I would vote for improving the documentation.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Documentation on tuple-type data in DataArrays 692106936

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