issue_comments
2 rows where issue = 47366080 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Automatically fall-back to pydap for opendap queries · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
107250264 | https://github.com/pydata/xarray/issues/272#issuecomment-107250264 | https://api.github.com/repos/pydata/xarray/issues/272 | MDEyOklzc3VlQ29tbWVudDEwNzI1MDI2NA== | shoyer 1217238 | 2015-05-31T21:52:03Z | 2015-05-31T21:52:03Z | MEMBER | This is complete, see: https://github.com/xray/xray/commit/fa0441ae807ffa264a5c72466c185833299285f6 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Automatically fall-back to pydap for opendap queries 47366080 | |
83253988 | https://github.com/pydata/xarray/issues/272#issuecomment-83253988 | https://api.github.com/repos/pydata/xarray/issues/272 | MDEyOklzc3VlQ29tbWVudDgzMjUzOTg4 | shoyer 1217238 | 2015-03-19T01:40:25Z | 2015-03-19T01:40:25Z | MEMBER | 333 fixed this issue for the scipy backend. We still should do this for pydap, though (or at least allow |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Automatically fall-back to pydap for opendap queries 47366080 |
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