issue_comments
3 rows where issue = 462010865 and user = 6628425 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- How to select using `.where()` on a timestamp `coordinate` for forecast data with 5 dimensions · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
508992414 | https://github.com/pydata/xarray/issues/3053#issuecomment-508992414 | https://api.github.com/repos/pydata/xarray/issues/3053 | MDEyOklzc3VlQ29tbWVudDUwODk5MjQxNA== | spencerkclark 6628425 | 2019-07-07T11:36:04Z | 2019-07-07T11:36:04Z | MEMBER | Glad I could help! Feel free to close this issue if you don't have any further questions on this topic (you'll still be able to refer to it later). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
How to select using `.where()` on a timestamp `coordinate` for forecast data with 5 dimensions 462010865 | |
506747197 | https://github.com/pydata/xarray/issues/3053#issuecomment-506747197 | https://api.github.com/repos/pydata/xarray/issues/3053 | MDEyOklzc3VlQ29tbWVudDUwNjc0NzE5Nw== | spencerkclark 6628425 | 2019-06-28T14:07:40Z | 2019-06-28T14:07:40Z | MEMBER | Sure thing -- that's a valid concern. Perhaps it makes sense then to retain the MultiIndex that gets created through stacking:
|
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 1, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
How to select using `.where()` on a timestamp `coordinate` for forecast data with 5 dimensions 462010865 | |
506725234 | https://github.com/pydata/xarray/issues/3053#issuecomment-506725234 | https://api.github.com/repos/pydata/xarray/issues/3053 | MDEyOklzc3VlQ29tbWVudDUwNjcyNTIzNA== | spencerkclark 6628425 | 2019-06-28T13:01:03Z | 2019-06-28T13:01:58Z | MEMBER | Thanks for the easy to copy and paste example. In the Under that assumption, I think the simplest approach is to stack the |
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 1, "rocket": 0, "eyes": 0 } |
How to select using `.where()` on a timestamp `coordinate` for forecast data with 5 dimensions 462010865 |
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