issue_comments
2 rows where issue = 33942756 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- keep attrs when reducing xray objects · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 43784177 | https://github.com/pydata/xarray/issues/138#issuecomment-43784177 | https://api.github.com/repos/pydata/xarray/issues/138 | MDEyOklzc3VlQ29tbWVudDQzNzg0MTc3 | shoyer 1217238 | 2014-05-21T16:52:26Z | 2014-05-21T16:52:26Z | MEMBER | @ebrevdo This is for reduce operations like "mean" which are unary operators. But it does seem like a good idea to consider if/how this could be extended to binary operations (e.g., "merge" or "add"). To make this an option for mathematical operations like "add" we would need to add an |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
keep attrs when reducing xray objects 33942756 | |
| 43710580 | https://github.com/pydata/xarray/issues/138#issuecomment-43710580 | https://api.github.com/repos/pydata/xarray/issues/138 | MDEyOklzc3VlQ29tbWVudDQzNzEwNTgw | shoyer 1217238 | 2014-05-21T04:10:33Z | 2014-05-21T04:10:33Z | MEMBER | This seems fine by me. @akleeman Your thoughts? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
keep attrs when reducing xray objects 33942756 |
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