issue_comments
2 rows where issue = 860418546 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- N-dimensional boolean indexing · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 824505721 | https://github.com/pydata/xarray/issues/5179#issuecomment-824505721 | https://api.github.com/repos/pydata/xarray/issues/5179 | MDEyOklzc3VlQ29tbWVudDgyNDUwNTcyMQ== | shoyer 1217238 | 2021-04-22T03:11:21Z | 2021-04-22T03:11:21Z | MEMBER | @max-sixty and I have been having some more discussion about whether this is what But regardless of what we want boolean indexing with |
{
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
N-dimensional boolean indexing 860418546 | |
| 823674011 | https://github.com/pydata/xarray/issues/5179#issuecomment-823674011 | https://api.github.com/repos/pydata/xarray/issues/5179 | MDEyOklzc3VlQ29tbWVudDgyMzY3NDAxMQ== | shoyer 1217238 | 2021-04-20T23:51:46Z | 2021-04-20T23:51:46Z | MEMBER | I wonder if this is just a better proposal than making N-dimensional boolean indexing an alias for |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
N-dimensional boolean indexing 860418546 |
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