issue_comments
2 rows where issue = 608923222 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Add NetCDF3 dtype coercion for unsigned integer types · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 622086349 | https://github.com/pydata/xarray/issues/4014#issuecomment-622086349 | https://api.github.com/repos/pydata/xarray/issues/4014 | MDEyOklzc3VlQ29tbWVudDYyMjA4NjM0OQ== | dcherian 2448579 | 2020-04-30T20:17:12Z | 2020-04-30T20:17:12Z | MEMBER | This sounds reasonable to me |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Add NetCDF3 dtype coercion for unsigned integer types 608923222 | |
| 621102297 | https://github.com/pydata/xarray/issues/4014#issuecomment-621102297 | https://api.github.com/repos/pydata/xarray/issues/4014 | MDEyOklzc3VlQ29tbWVudDYyMTEwMjI5Nw== | blsqr 1700203 | 2020-04-29T09:56:11Z | 2020-04-29T09:56:11Z | CONTRIBUTOR | I'd be happy to open a PR, if such a behaviour is desired. It seems like extending the Suggestion: Add all |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Add NetCDF3 dtype coercion for unsigned integer types 608923222 |
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 2