issue_comments
1 row where user = 397386 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 495600572 | https://github.com/pydata/xarray/issues/2986#issuecomment-495600572 | https://api.github.com/repos/pydata/xarray/issues/2986 | MDEyOklzc3VlQ29tbWVudDQ5NTYwMDU3Mg== | fbriol 397386 | 2019-05-24T12:19:14Z | 2019-05-24T12:19:14Z | CONTRIBUTOR | Thank you, for the information, I will try to interface my classes with this information. I saw in the conversation that one of the problems was the serialization of this information in NetCDF files. My class allows you to serialize the tree:
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
How to add a custom indexer. 448082431 |
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