issue_comments
2 rows where issue = 193294729 and user = 10050469 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: updated_at (date)
issue 1
- Scalar coords seep into index coords · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
264913502 | https://github.com/pydata/xarray/issues/1152#issuecomment-264913502 | https://api.github.com/repos/pydata/xarray/issues/1152 | MDEyOklzc3VlQ29tbWVudDI2NDkxMzUwMg== | fmaussion 10050469 | 2016-12-05T17:09:34Z | 2016-12-05T17:09:34Z | MEMBER |
Yes. What I meant with my yesterday's late night answer is that keeping the coordinates around could be most useful when using irregular coordinates... |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Scalar coords seep into index coords 193294729 | |
264737209 | https://github.com/pydata/xarray/issues/1152#issuecomment-264737209 | https://api.github.com/repos/pydata/xarray/issues/1152 | MDEyOklzc3VlQ29tbWVudDI2NDczNzIwOQ== | fmaussion 10050469 | 2016-12-04T22:35:54Z | 2016-12-04T22:35:54Z | MEMBER | I think it's fine. Coordinates sometimes need to be defined by paired coords too:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Scalar coords seep into index coords 193294729 |
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