issue_comments
1 row where user = 74330736 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
812212847 | https://github.com/pydata/xarray/issues/3564#issuecomment-812212847 | https://api.github.com/repos/pydata/xarray/issues/3564 | MDEyOklzc3VlQ29tbWVudDgxMjIxMjg0Nw== | apkrelling 74330736 | 2021-04-01T22:33:57Z | 2021-04-01T22:33:57Z | CONTRIBUTOR | Hello everyone, is this issue still relevant? I could add a domain-use case for oceanography or meteorology, but it seems like that has already been done under
1) So there's no need to work on domain-use cases for oceanography or meteorology, is that correct? 2) Also, I'd be happy to contribute with something about how to migrate from numpy to xarray, if that is still needed. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DOC: from examples to tutorials 527323165 |
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