issue_comments
1 row where issue = 322445312 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
These facets timed out: issue
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 388922657 | https://github.com/pydata/xarray/issues/2121#issuecomment-388922657 | https://api.github.com/repos/pydata/xarray/issues/2121 | MDEyOklzc3VlQ29tbWVudDM4ODkyMjY1Nw== | shoyer 1217238 | 2018-05-14T18:47:55Z | 2018-05-14T18:47:55Z | MEMBER | The simplest design here would be to extract the logic from DataStorePickleMixin into a pickleable wrapper class that could be used in e.g., instead of
Eventually, we should probably refactor xarray's existing data stores to use this -- the current logic is really messy/hard to understand. We'll probably also want to eventually factor out the auto-close logic in some composable way, but that can be saved for later. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
rasterio backend should use DataStorePickleMixin (or something similar) 322445312 |
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