issue_comments
1 row where issue = 224878728 and user = 23484003 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- argmin / argmax behavior doesn't match documentation · 1 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 298253809 | https://github.com/pydata/xarray/issues/1388#issuecomment-298253809 | https://api.github.com/repos/pydata/xarray/issues/1388 | MDEyOklzc3VlQ29tbWVudDI5ODI1MzgwOQ== | lamorton 23484003 | 2017-04-30T20:08:25Z | 2017-04-30T20:08:25Z | NONE | Well, The next question is, what happens if you start supplying coordinate/dimension optional arguments to Does that seem reasonable? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
argmin / argmax behavior doesn't match documentation 224878728 |
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