issue_comments
6 rows where author_association = "MEMBER" and issue = 104484316 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- CDO-like convenience methods to select times · 6 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
427335183 | https://github.com/pydata/xarray/issues/557#issuecomment-427335183 | https://api.github.com/repos/pydata/xarray/issues/557 | MDEyOklzc3VlQ29tbWVudDQyNzMzNTE4Mw== | shoyer 1217238 | 2018-10-05T11:33:45Z | 2018-10-05T11:33:45Z | MEMBER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
CDO-like convenience methods to select times 104484316 | |
427279439 | https://github.com/pydata/xarray/issues/557#issuecomment-427279439 | https://api.github.com/repos/pydata/xarray/issues/557 | MDEyOklzc3VlQ29tbWVudDQyNzI3OTQzOQ== | shoyer 1217238 | 2018-10-05T07:59:47Z | 2018-10-05T08:00:28Z | MEMBER | I don’t think there’s an easy way to this with vectorized indexing, but if we supported multidimensional indexing with boolean keys as proposed in https://github.com/pydata/xarray/issues/1887 (equivalent to where with drop=True) we could write |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
CDO-like convenience methods to select times 104484316 | |
427078606 | https://github.com/pydata/xarray/issues/557#issuecomment-427078606 | https://api.github.com/repos/pydata/xarray/issues/557 | MDEyOklzc3VlQ29tbWVudDQyNzA3ODYwNg== | rabernat 1197350 | 2018-10-04T16:12:43Z | 2018-10-04T16:12:43Z | MEMBER | Is there a way to do this easily now with vectorized indexing? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
CDO-like convenience methods to select times 104484316 | |
137257727 | https://github.com/pydata/xarray/issues/557#issuecomment-137257727 | https://api.github.com/repos/pydata/xarray/issues/557 | MDEyOklzc3VlQ29tbWVudDEzNzI1NzcyNw== | jhamman 2443309 | 2015-09-02T21:57:54Z | 2015-09-02T21:57:54Z | MEMBER | I'd also like to see this come into being. My two cents on the syntax is that your second idea is best:
I don't care much for option 3 since the variable name is being used as an attribute (what if my time variable is called "Times"?). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
CDO-like convenience methods to select times 104484316 | |
137182504 | https://github.com/pydata/xarray/issues/557#issuecomment-137182504 | https://api.github.com/repos/pydata/xarray/issues/557 | MDEyOklzc3VlQ29tbWVudDEzNzE4MjUwNA== | shoyer 1217238 | 2015-09-02T17:37:56Z | 2015-09-02T17:37:56Z | MEMBER | Currently, the way to do this is to create a boolean indexer, with something like the following:
I agree that this is overly verbose and we can come up with something better. I'm not quite happy with Something like So, some other possible ways to spell this:
1. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
CDO-like convenience methods to select times 104484316 | |
137134794 | https://github.com/pydata/xarray/issues/557#issuecomment-137134794 | https://api.github.com/repos/pydata/xarray/issues/557 | MDEyOklzc3VlQ29tbWVudDEzNzEzNDc5NA== | clarkfitzg 5356122 | 2015-09-02T15:32:17Z | 2015-09-02T15:32:17Z | MEMBER | Just curious- how would we currently do this? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
CDO-like convenience methods to select times 104484316 |
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 4