issue_comments
2 rows where issue = 322849322 and user = 4849151 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Using `DataArray.where()` with a DataArray as the condition drops the name · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 613313818 | https://github.com/pydata/xarray/issues/2129#issuecomment-613313818 | https://api.github.com/repos/pydata/xarray/issues/2129 | MDEyOklzc3VlQ29tbWVudDYxMzMxMzgxOA== | jacklovell 4849151 | 2020-04-14T08:54:33Z | 2020-04-14T08:54:33Z | NONE | This bug appears to have been fixed, as of Xarray 0.15.0. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Using `DataArray.where()` with a DataArray as the condition drops the name 322849322 | |
| 389079066 | https://github.com/pydata/xarray/issues/2129#issuecomment-389079066 | https://api.github.com/repos/pydata/xarray/issues/2129 | MDEyOklzc3VlQ29tbWVudDM4OTA3OTA2Ng== | jacklovell 4849151 | 2018-05-15T08:00:31Z | 2018-05-15T08:00:31Z | NONE | Yes, I think it makes sense to couple it with |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Using `DataArray.where()` with a DataArray as the condition drops the name 322849322 |
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