issue_comments
1 row where issue = 58117200 and user = 5356122 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Support multi-dimensional grouped operations and group_over · 1 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 131891348 | https://github.com/pydata/xarray/issues/324#issuecomment-131891348 | https://api.github.com/repos/pydata/xarray/issues/324 | MDEyOklzc3VlQ29tbWVudDEzMTg5MTM0OA== | clarkfitzg 5356122 | 2015-08-17T17:04:44Z | 2015-08-17T17:04:44Z | MEMBER | For (2) I think it makes sense to extend the existing groupby to deal with multiple dimensions. Ie, let it take an iterable of dimension names. ```
Then we'd have something similar to the SQL groupby, which is a good thing. By the way, in #527 we were considering using this approach to make the faceted plots on both rows and columns. |
{
"total_count": 4,
"+1": 4,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Support multi-dimensional grouped operations and group_over 58117200 |
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