issue_comments
2 rows where issue = 535812301 and user = 2448579 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- Timedelta dt accessor does not work · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
564714249 | https://github.com/pydata/xarray/issues/3609#issuecomment-564714249 | https://api.github.com/repos/pydata/xarray/issues/3609 | MDEyOklzc3VlQ29tbWVudDU2NDcxNDI0OQ== | dcherian 2448579 | 2019-12-11T20:16:19Z | 2019-12-11T20:16:19Z | MEMBER | I think this would be a welcome feature. It seems like there should be a lot of shared code between the two accessors. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Timedelta dt accessor does not work 535812301 | |
564705838 | https://github.com/pydata/xarray/issues/3609#issuecomment-564705838 | https://api.github.com/repos/pydata/xarray/issues/3609 | MDEyOklzc3VlQ29tbWVudDU2NDcwNTgzOA== | dcherian 2448579 | 2019-12-11T19:53:49Z | 2019-12-11T19:53:49Z | MEMBER | This is more unimplemented feature than a bug. The Timedelta functionality hasn't been implemented e.g. https://github.com/pydata/xarray/blob/2ee89c36a7ed512a221d38e09e7637429ced22d3/xarray/core/accessor_dt.py#L204 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Timedelta dt accessor does not work 535812301 |
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