issue_comments
2 rows where issue = 407864596 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- silence warning for decode_cf_datetime? · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
461983092 | https://github.com/pydata/xarray/issues/2754#issuecomment-461983092 | https://api.github.com/repos/pydata/xarray/issues/2754 | MDEyOklzc3VlQ29tbWVudDQ2MTk4MzA5Mg== | shoyer 1217238 | 2019-02-08T23:33:37Z | 2019-02-08T23:33:37Z | MEMBER | From a design perspective, I would consider adding an optional |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
silence warning for decode_cf_datetime? 407864596 | |
461982693 | https://github.com/pydata/xarray/issues/2754#issuecomment-461982693 | https://api.github.com/repos/pydata/xarray/issues/2754 | MDEyOklzc3VlQ29tbWVudDQ2MTk4MjY5Mw== | shoyer 1217238 | 2019-02-08T23:31:23Z | 2019-02-08T23:31:23Z | MEMBER | +1 for adding an option to always use CF datetimes. I would probably start with putting it on |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
silence warning for decode_cf_datetime? 407864596 |
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