issue_comments
2 rows where issue = 1644429340 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Feature proposal: DataArray.to_zarr() · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1487609291 | https://github.com/pydata/xarray/issues/7692#issuecomment-1487609291 | https://api.github.com/repos/pydata/xarray/issues/7692 | IC_kwDOAMm_X85Yqx3L | keewis 14808389 | 2023-03-28T21:21:47Z | 2023-03-28T21:21:47Z | MEMBER | As far as I understand #5954 and the meeting notes, we didn't decide anything about that yet (I might be wrong, though). So I assume the only reason we don't have write backends and |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Feature proposal: DataArray.to_zarr() 1644429340 | |
1487433218 | https://github.com/pydata/xarray/issues/7692#issuecomment-1487433218 | https://api.github.com/repos/pydata/xarray/issues/7692 | IC_kwDOAMm_X85YqG4C | keewis 14808389 | 2023-03-28T18:44:39Z | 2023-03-28T18:44:39Z | MEMBER | I guess the alternative would be to go with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Feature proposal: DataArray.to_zarr() 1644429340 |
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