issue_comments
2 rows where issue = 930925407 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Faster transpose · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 869213523 | https://github.com/pydata/xarray/pull/5541#issuecomment-869213523 | https://api.github.com/repos/pydata/xarray/issues/5541 | MDEyOklzc3VlQ29tbWVudDg2OTIxMzUyMw== | max-sixty 5635139 | 2021-06-27T19:31:06Z | 2021-06-27T19:31:06Z | MEMBER |
It looks like they're on the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Faster transpose 930925407 | |
| 869213401 | https://github.com/pydata/xarray/pull/5541#issuecomment-869213401 | https://api.github.com/repos/pydata/xarray/issues/5541 | MDEyOklzc3VlQ29tbWVudDg2OTIxMzQwMQ== | max-sixty 5635139 | 2021-06-27T19:29:48Z | 2021-06-27T19:29:48Z | MEMBER | This makes sense! No strong view on the 1D copy — I guess it's a performance vs simplicity tradeoff. I don't think there's an existing ASV but we could create one if we want to work more on this. I'll merge this, thank you @Illviljan ! |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Faster transpose 930925407 |
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