issue_comments
2 rows where issue = 276241764 and user = 2443309 sorted by updated_at descending
This data as json, CSV (advanced)
These facets timed out: author_association, issue
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
350145043 | https://github.com/pydata/xarray/issues/1739#issuecomment-350145043 | https://api.github.com/repos/pydata/xarray/issues/1739 | MDEyOklzc3VlQ29tbWVudDM1MDE0NTA0Mw== | jhamman 2443309 | 2017-12-08T01:25:21Z | 2017-12-08T01:25:21Z | MEMBER | What if we just supplied an |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Utility to restore original dimension order after apply_ufunc 276241764 | |
347078577 | https://github.com/pydata/xarray/issues/1739#issuecomment-347078577 | https://api.github.com/repos/pydata/xarray/issues/1739 | MDEyOklzc3VlQ29tbWVudDM0NzA3ODU3Nw== | jhamman 2443309 | 2017-11-27T04:54:03Z | 2017-11-27T04:54:03Z | MEMBER | At this point, I think I'm +1 on either automatically restoring dimension order or providing some option to do so (with restoring as the default). I'm still getting used to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Utility to restore original dimension order after apply_ufunc 276241764 |
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