issue_comments
1 row where issue = 161991202 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- BUG: Dataset constructor puts lists in coords rather that data_vars · 1 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 228408435 | https://github.com/pydata/xarray/issues/890#issuecomment-228408435 | https://api.github.com/repos/pydata/xarray/issues/890 | MDEyOklzc3VlQ29tbWVudDIyODQwODQzNQ== | shoyer 1217238 | 2016-06-24T17:27:56Z | 2016-06-24T17:27:56Z | MEMBER | This may not be clearly documented, but it is/was intentional behavior. To be clear, there are two things going on here:
1. Arguments like Originally, this made sense because we didn't have a separate |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
BUG: Dataset constructor puts lists in coords rather that data_vars 161991202 |
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