issue_comments
5 rows where issue = 84068169 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- select range/ slice with method='nearest' · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
454533545 | https://github.com/pydata/xarray/issues/418#issuecomment-454533545 | https://api.github.com/repos/pydata/xarray/issues/418 | MDEyOklzc3VlQ29tbWVudDQ1NDUzMzU0NQ== | max-sixty 5635139 | 2019-01-15T20:10:19Z | 2019-01-15T20:10:19Z | MEMBER | Closing as stale, please reopen if still relevant |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
select range/ slice with method='nearest' 84068169 | |
111943792 | https://github.com/pydata/xarray/issues/418#issuecomment-111943792 | https://api.github.com/repos/pydata/xarray/issues/418 | MDEyOklzc3VlQ29tbWVudDExMTk0Mzc5Mg== | mathause 10194086 | 2015-06-15T06:17:41Z | 2015-06-15T06:17:41Z | MEMBER | ok thank you for looking at it and the clarification. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
select range/ slice with method='nearest' 84068169 | |
111630149 | https://github.com/pydata/xarray/issues/418#issuecomment-111630149 | https://api.github.com/repos/pydata/xarray/issues/418 | MDEyOklzc3VlQ29tbWVudDExMTYzMDE0OQ== | shoyer 1217238 | 2015-06-12T22:07:30Z | 2015-06-12T22:09:16Z | MEMBER | I just clarified this in the docs: http://xray.readthedocs.org/en/stable/indexing.html#nearest-neighbor-lookups Let me know if that makes sense -- hopefully it's clear now that you actually don't need |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
select range/ slice with method='nearest' 84068169 | |
108119362 | https://github.com/pydata/xarray/issues/418#issuecomment-108119362 | https://api.github.com/repos/pydata/xarray/issues/418 | MDEyOklzc3VlQ29tbWVudDEwODExOTM2Mg== | shoyer 1217238 | 2015-06-02T22:43:38Z | 2015-06-02T22:43:38Z | MEMBER |
This inconsistency is definitely a little annoying, though -- I don't see any harm in support nearest neighbor lookups for the bounds. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
select range/ slice with method='nearest' 84068169 | |
108014220 | https://github.com/pydata/xarray/issues/418#issuecomment-108014220 | https://api.github.com/repos/pydata/xarray/issues/418 | MDEyOklzc3VlQ29tbWVudDEwODAxNDIyMA== | mathause 10194086 | 2015-06-02T16:57:52Z | 2015-06-02T16:58:52Z | MEMBER | I did a short hack - not sure if it is of any help... 420
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
select range/ slice with method='nearest' 84068169 |
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 3