issue_comments
2 rows where issue = 201884828 and user = 327925 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Fix docs · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
273824430 | https://github.com/pydata/xarray/pull/1220#issuecomment-273824430 | https://api.github.com/repos/pydata/xarray/issues/1220 | MDEyOklzc3VlQ29tbWVudDI3MzgyNDQzMA== | takluyver 327925 | 2017-01-19T16:28:47Z | 2017-01-19T16:28:47Z | MEMBER | I just made ipython/ipython#10186 - if you've got time, could you try with that branch and see if it works without the config? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix docs 201884828 | |
273801697 | https://github.com/pydata/xarray/pull/1220#issuecomment-273801697 | https://api.github.com/repos/pydata/xarray/issues/1220 | MDEyOklzc3VlQ29tbWVudDI3MzgwMTY5Nw== | takluyver 327925 | 2017-01-19T15:12:55Z | 2017-01-19T15:12:55Z | MEMBER | I'm still a bit puzzled why this is necessary. I couldn't reproduce it when building the docs locally. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix docs 201884828 |
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