issue_comments
2 rows where issue = 448082431 and user = 4160723 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- How to add a custom indexer. · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
495590898 | https://github.com/pydata/xarray/issues/2986#issuecomment-495590898 | https://api.github.com/repos/pydata/xarray/issues/2986 | MDEyOklzc3VlQ29tbWVudDQ5NTU5MDg5OA== | benbovy 4160723 | 2019-05-24T11:50:49Z | 2019-05-24T11:50:49Z | MEMBER | See also #1603 where general discussions happen on this topic. |
{ "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 | |
495589522 | https://github.com/pydata/xarray/issues/2986#issuecomment-495589522 | https://api.github.com/repos/pydata/xarray/issues/2986 | MDEyOklzc3VlQ29tbWVudDQ5NTU4OTUyMg== | benbovy 4160723 | 2019-05-24T11:46:46Z | 2019-05-24T11:46:46Z | MEMBER | Hi @fbriol, It would be indeed really nice to add custom indexes to xarray like R*Tree! Unfortunately, this isn't supported right now, but it's one of the main points in xarray's development roadmap. @shoyer has started working on this in #2195. |
{ "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