issue_comments
1 row where author_association = "NONE", issue = 324740017 and user = 810663 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- holoviews / bokeh doesn't like cftime coords · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
404830736 | https://github.com/pydata/xarray/issues/2164#issuecomment-404830736 | https://api.github.com/repos/pydata/xarray/issues/2164 | MDEyOklzc3VlQ29tbWVudDQwNDgzMDczNg== | pelson 810663 | 2018-07-13T13:17:44Z | 2018-07-13T13:17:44Z | NONE |
Why a separate package and not in nc-time-axis? (Or alternatively, just in cftime, as you say) FWIW https://github.com/SciTools/nc-time-axis/issues/16 tried to get the ball rolling on clarifications around the CalendarDateTime object. That was necessary in the days when there was a single PhoneyDateTime object, that didn't have calendar information associated with it. It seems that some refactoring is very plausible in nc-time-axis at this point. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
holoviews / bokeh doesn't like cftime coords 324740017 |
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