issue_comments
1 row where issue = 636029447 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- xarray.where changes dimension order · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
649968866 | https://github.com/pydata/xarray/issues/4136#issuecomment-649968866 | https://api.github.com/repos/pydata/xarray/issues/4136 | MDEyOklzc3VlQ29tbWVudDY0OTk2ODg2Ng== | shoyer 1217238 | 2020-06-26T05:05:48Z | 2020-06-26T05:05:48Z | MEMBER | Dimensions on the outputs of an xarray operations are picked based on their order of appearance in the arguments. In this case, I agree that it's somewhat surprising, but putting If you want to preserve the original dimensions order, one way to achieve this would be to use the
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray.where changes dimension order 636029447 |
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