issue_comments
2 rows where issue = 49755539 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Proposal: allow tuples instead of slice objects in sel or isel · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
75680737 | https://github.com/pydata/xarray/issues/280#issuecomment-75680737 | https://api.github.com/repos/pydata/xarray/issues/280 | MDEyOklzc3VlQ29tbWVudDc1NjgwNzM3 | shoyer 1217238 | 2015-02-24T01:22:12Z | 2015-02-24T01:22:12Z | MEMBER | OK, closing. The real fix here will require new Python syntax to support |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Proposal: allow tuples instead of slice objects in sel or isel 49755539 | |
66738105 | https://github.com/pydata/xarray/issues/280#issuecomment-66738105 | https://api.github.com/repos/pydata/xarray/issues/280 | MDEyOklzc3VlQ29tbWVudDY2NzM4MTA1 | shoyer 1217238 | 2014-12-12T06:48:15Z | 2014-12-12T06:48:15Z | MEMBER | Two concerns occur to me about this change: 1. It does break backward compatibility. 2. It currently possible to use an index of tuples (and eventually, we'll support multi-index), and this would break that. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Proposal: allow tuples instead of slice objects in sel or isel 49755539 |
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