issue_comments

Table actions

1 row where author_association = "MEMBER" and issue = 245893358 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

  • ENH: points coord from isel/sel_points should be a MultiIndex · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
318426619 https://github.com/pydata/xarray/issues/1493#issuecomment-318426619 https://api.github.com/repos/pydata/xarray/issues/1493 MDEyOklzc3VlQ29tbWVudDMxODQyNjYxOQ== shoyer 1217238 2017-07-27T17:11:37Z 2017-07-27T17:11:37Z MEMBER

If we can finish up @fujiisoup's work (https://github.com/pydata/xarray/pull/1473) bringing indexing with broadcasting to xarray, then we can possibly do away with sel_points and isel_points instead.

This doesn't resolve the issue of whether the indexed coordinates should be in a MultiIndex or not. This does make a certain amount of sense, but to be honest, I'm a little divided here -- I'm still not entirely happy with how MultiIndex works in xarray (see https://github.com/pydata/xarray/pull/1426 for more discussion).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: points coord from isel/sel_points should be a MultiIndex 245893358

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