issue_comments
2 rows where author_association = "MEMBER", issue = 72145600 and user = 2443309 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: updated_at (date)
issue 1
- millisecond and microseconds support · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 97896201 | https://github.com/pydata/xarray/issues/406#issuecomment-97896201 | https://api.github.com/repos/pydata/xarray/issues/406 | MDEyOklzc3VlQ29tbWVudDk3ODk2MjAx | jhamman 2443309 | 2015-04-30T17:48:47Z | 2015-04-30T17:48:47Z | MEMBER | My thoughts exactly. The original post mentioned |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
millisecond and microseconds support 72145600 | |
| 97892365 | https://github.com/pydata/xarray/issues/406#issuecomment-97892365 | https://api.github.com/repos/pydata/xarray/issues/406 | MDEyOklzc3VlQ29tbWVudDk3ODkyMzY1 | jhamman 2443309 | 2015-04-30T17:38:15Z | 2015-04-30T17:38:15Z | MEMBER | As a small side note, netcdf4-python doesn't exactly support microseconds. There is a known precision issue that ends up giving |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
millisecond and microseconds support 72145600 |
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