issue_comments
1 row where issue = 38110382 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Automatic label alignment · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
73464476 | https://github.com/pydata/xarray/issues/186#issuecomment-73464476 | https://api.github.com/repos/pydata/xarray/issues/186 | MDEyOklzc3VlQ29tbWVudDczNDY0NDc2 | shoyer 1217238 | 2015-02-09T06:48:28Z | 2015-02-09T06:48:28Z | MEMBER | I have most of a working implementation for this that will be up for a PR shortly. Here's some of my thinking on expected behavior. Based on the principle that combining arrays into a new dataset should not remove information, it makes sense to use outer joins for When adding an item to an existing dataset, it would be surprising if indexes or dimension sizes changed. So I think we should be using left joins for Right now, we use |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Automatic label alignment 38110382 |
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