issue_comments
2 rows where issue = 266133430 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: updated_at (date)
issue 1
- DataArray.argsort should be deleted · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
337631240 | https://github.com/pydata/xarray/issues/1635#issuecomment-337631240 | https://api.github.com/repos/pydata/xarray/issues/1635 | MDEyOklzc3VlQ29tbWVudDMzNzYzMTI0MA== | shoyer 1217238 | 2017-10-18T15:31:56Z | 2017-10-18T15:31:56Z | MEMBER |
I'm not a huge fan of auto-flattening for xarray, but I can see this logic.
I would probably implement a new method for this, maybe |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DataArray.argsort should be deleted 266133430 | |
337387398 | https://github.com/pydata/xarray/issues/1635#issuecomment-337387398 | https://api.github.com/repos/pydata/xarray/issues/1635 | MDEyOklzc3VlQ29tbWVudDMzNzM4NzM5OA== | shoyer 1217238 | 2017-10-17T22:04:26Z | 2017-10-17T22:19:51Z | MEMBER | It seems like another reasonable choice would be for I think this internal utility function is equivalent to your second argsort: https://github.com/pydata/xarray/blob/2949558b75a65404a500a237ec54834fd6946d07/xarray/core/nputils.py#L38-L55 In practice, we might use |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DataArray.argsort should be deleted 266133430 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1