issue_comments

Table actions

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

  • Clarifying sel/drop behavior for dims with vs. without coords · 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
277387768 https://github.com/pydata/xarray/issues/1248#issuecomment-277387768 https://api.github.com/repos/pydata/xarray/issues/1248 MDEyOklzc3VlQ29tbWVudDI3NzM4Nzc2OA== shoyer 1217238 2017-02-03T23:08:21Z 2017-02-03T23:08:21Z MEMBER

It would help me understand how this violates your expectations if you could write this in terms of single method calls, e.g., .isel or .drop (not both).

Note that v0.9.1 contains the new drop argument to .isel for exactly these sorts of use cases: ds.isel(dim_0, drop=True) should work regardless of whether or not there is a dim_0 coordinate.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Clarifying sel/drop behavior for dims with vs. without coords 205248365

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