issue_comments

Table actions

1 row where issue = 178887041 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)

These facets timed out: author_association

user 1

  • shoyer · 1 ✖

issue 1

  • DataArray coords: tuple vs. list · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
249233747 https://github.com/pydata/xarray/issues/1016#issuecomment-249233747 https://api.github.com/repos/pydata/xarray/issues/1016 MDEyOklzc3VlQ29tbWVudDI0OTIzMzc0Nw== shoyer 1217238 2016-09-23T16:06:37Z 2016-09-23T16:06:37Z MEMBER

Tuples are overloaded so you can avoid writing another constructor -- they're interpreted as (dims, data[, attrs]), e.g., as described in the Dataset constructor. Otherwise it gets quite verbose to specify coordinates with dimensions.

Looking at the docs more carefully, we do mention this in the general overview of data structures, but not the API docs for DataArray.__init__. We should probably fix that.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   DataArray coords: tuple vs. list 178887041

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