issue_comments
1 row where author_association = "MEMBER", issue = 309686915 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
These facets timed out: author_association
issue 1
- square-bracket slice a Dataset with a DataArray · 1 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 377314912 | https://github.com/pydata/xarray/issues/2027#issuecomment-377314912 | https://api.github.com/repos/pydata/xarray/issues/2027 | MDEyOklzc3VlQ29tbWVudDM3NzMxNDkxMg== | shoyer 1217238 | 2018-03-29T17:40:30Z | 2018-03-29T17:40:30Z | MEMBER | I think the short answer why we don't support this is that with This might be clearer with integer indexing. We support indexing like However, we could potentially support this as a form of "multi-dimensional boolean indexing" (https://github.com/pydata/xarray/issues/1887). Basically, |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
square-bracket slice a Dataset with a DataArray 309686915 |
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