issue_comments

Table actions

1 row where issue = 46756098 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

These facets timed out: author_association, issue

user 1

  • shoyer · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
60422237 https://github.com/pydata/xarray/issues/266#issuecomment-60422237 https://api.github.com/repos/pydata/xarray/issues/266 MDEyOklzc3VlQ29tbWVudDYwNDIyMjM3 shoyer 1217238 2014-10-24T17:37:12Z 2015-02-18T19:33:16Z MEMBER

Right now we have the 1d version of slices with groupby, e.g.,

for _, sl in data.groupby('raa'): # work with DataArray with coordinates (wl, sza, vza)

(though the code does sort of implicitly assume that the values along the index are unique)

I agree, something like this would be nice. I think Iris now also has slices_over, e.g., data.slices_over(['sza', 'vza']) would be equivalent to your example, and it would be good to cover that case as well.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Easy iteration over slices of a DataArray 46756098

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