issue_comments
3 rows where author_association = "MEMBER", issue = 427644858 and user = 10050469 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date)
issue 1
- WHERE function, problems with memory operations? · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
478570138 | https://github.com/pydata/xarray/issues/2861#issuecomment-478570138 | https://api.github.com/repos/pydata/xarray/issues/2861 | MDEyOklzc3VlQ29tbWVudDQ3ODU3MDEzOA== | fmaussion 10050469 | 2019-04-01T13:03:34Z | 2019-04-01T13:03:34Z | MEMBER | Thanks, I could download them. Can you tell us what the problem with these files is, that we might have to solve in xarray? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WHERE function, problems with memory operations? 427644858 | |
478546784 | https://github.com/pydata/xarray/issues/2861#issuecomment-478546784 | https://api.github.com/repos/pydata/xarray/issues/2861 | MDEyOklzc3VlQ29tbWVudDQ3ODU0Njc4NA== | fmaussion 10050469 | 2019-04-01T11:47:27Z | 2019-04-01T11:47:27Z | MEMBER |
All xarray operations will return xarray objects. And xarray will try to match coordinates wherever possible.
In your example above, they are not. Can you help us to reproduce the error with a Minimal Complete Verifiable Example? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WHERE function, problems with memory operations? 427644858 | |
478538543 | https://github.com/pydata/xarray/issues/2861#issuecomment-478538543 | https://api.github.com/repos/pydata/xarray/issues/2861 | MDEyOklzc3VlQ29tbWVudDQ3ODUzODU0Mw== | fmaussion 10050469 | 2019-04-01T11:17:46Z | 2019-04-01T11:19:28Z | MEMBER | xarray is "coordinate aware", i.e. it will try hard to prevent users doing bad things with non matching coordinates (yes, the fact that your If I understand what you want, this should do the trick:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WHERE function, problems with memory operations? 427644858 |
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