issue_comments
2 rows where issue = 437956917 and user = 9948595 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- fix multiIndex min max issue #2923 · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
487329592 | https://github.com/pydata/xarray/pull/2924#issuecomment-487329592 | https://api.github.com/repos/pydata/xarray/issues/2924 | MDEyOklzc3VlQ29tbWVudDQ4NzMyOTU5Mg== | arabidopsis 9948595 | 2019-04-28T00:21:15Z | 2019-04-28T00:21:15Z | CONTRIBUTOR | No problem. Thanks for xarray! Just a question. I put a guard in to test just for tuples (because that's what was breaking for me) but it seems to me that Wasn't sure. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fix multiIndex min max issue #2923 437956917 | |
487298047 | https://github.com/pydata/xarray/pull/2924#issuecomment-487298047 | https://api.github.com/repos/pydata/xarray/issues/2924 | MDEyOklzc3VlQ29tbWVudDQ4NzI5ODA0Nw== | arabidopsis 9948595 | 2019-04-27T16:04:45Z | 2019-04-27T16:04:45Z | CONTRIBUTOR | Oops... I usually use black -- which I turned off since it would really have stuffed the code :) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fix multiIndex min max issue #2923 437956917 |
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