issue_comments
2 rows where issue = 1644429340 and user = 2443309 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
1487709306 | https://github.com/pydata/xarray/issues/7692#issuecomment-1487709306 | https://api.github.com/repos/pydata/xarray/issues/7692 | IC_kwDOAMm_X85YrKR6 | jhamman 2443309 | 2023-03-28T22:58:30Z | 2023-03-28T22:58:30Z | MEMBER | Fair enough. I was extrapolating a bit based on the response to #7496. If someone wants to bite off the writable backends task, I'm all for it. |
{ "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 | |
1487524043 | https://github.com/pydata/xarray/issues/7692#issuecomment-1487524043 | https://api.github.com/repos/pydata/xarray/issues/7692 | IC_kwDOAMm_X85YqdDL | jhamman 2443309 | 2023-03-28T20:04:35Z | 2023-03-28T20:04:35Z | MEMBER | I was once a fan of the |
{ "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