issue_comments
2 rows where author_association = "MEMBER", issue = 279595497 and user = 2448579 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- ENH: Add dt.date accessor. · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
349559801 | https://github.com/pydata/xarray/pull/1762#issuecomment-349559801 | https://api.github.com/repos/pydata/xarray/issues/1762 | MDEyOklzc3VlQ29tbWVudDM0OTU1OTgwMQ== | dcherian 2448579 | 2017-12-06T07:39:53Z | 2017-12-06T07:39:53Z | MEMBER | Oh, I see your point. Once implemented, would the round/ceil/floor methods work as arguments to groupby too? That's really what I wanted to do. Are you in favor of renaming the current functionality to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
ENH: Add dt.date accessor. 279595497 | |
349509477 | https://github.com/pydata/xarray/pull/1762#issuecomment-349509477 | https://api.github.com/repos/pydata/xarray/issues/1762 | MDEyOklzc3VlQ29tbWVudDM0OTUwOTQ3Nw== | dcherian 2448579 | 2017-12-06T02:21:46Z | 2017-12-06T02:21:46Z | MEMBER | @shoyer Didn't know |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
ENH: Add dt.date accessor. 279595497 |
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