issue_comments
2 rows where issue = 728893769 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Support operations with pandas Offset objects · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
716067873 | https://github.com/pydata/xarray/issues/4535#issuecomment-716067873 | https://api.github.com/repos/pydata/xarray/issues/4535 | MDEyOklzc3VlQ29tbWVudDcxNjA2Nzg3Mw== | max-sixty 5635139 | 2020-10-24T23:21:49Z | 2020-10-24T23:21:49Z | MEMBER | Yes, good point, that would be easy and probably sufficient for most use-cases. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support operations with pandas Offset objects 728893769 | |
716066118 | https://github.com/pydata/xarray/issues/4535#issuecomment-716066118 | https://api.github.com/repos/pydata/xarray/issues/4535 | MDEyOklzc3VlQ29tbWVudDcxNjA2NjExOA== | dcherian 2448579 | 2020-10-24T22:59:56Z | 2020-10-24T23:00:30Z | MEMBER | For resample, we could add it to I agree with generally supporting adding pandas offset objects. EDIT: to clarify, |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support operations with pandas Offset objects 728893769 |
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 2