issue_comments
2 rows where issue = 694448177 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Keep the original ordering of the coordinates · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
687934050 | https://github.com/pydata/xarray/pull/4409#issuecomment-687934050 | https://api.github.com/repos/pydata/xarray/issues/4409 | MDEyOklzc3VlQ29tbWVudDY4NzkzNDA1MA== | max-sixty 5635139 | 2020-09-06T23:34:51Z | 2020-09-06T23:34:51Z | MEMBER |
Though I was thinking we wouldn't sort it; we'd take the order as given
I reckon it's fine, it's such a corner case, and it'll only affect these doctests |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Keep the original ordering of the coordinates 694448177 | |
687909934 | https://github.com/pydata/xarray/pull/4409#issuecomment-687909934 | https://api.github.com/repos/pydata/xarray/issues/4409 | MDEyOklzc3VlQ29tbWVudDY4NzkwOTkzNA== | max-sixty 5635139 | 2020-09-06T21:45:02Z | 2020-09-06T21:45:02Z | MEMBER | Could we keep them in sorted order like a normal |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Keep the original ordering of the coordinates 694448177 |
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