issue_comments
1 row where issue = 931591247 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Increase default `display_max_rows` · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
869763953 | https://github.com/pydata/xarray/issues/5545#issuecomment-869763953 | https://api.github.com/repos/pydata/xarray/issues/5545 | MDEyOklzc3VlQ29tbWVudDg2OTc2Mzk1Mw== | keewis 14808389 | 2021-06-28T15:06:23Z | 2021-06-28T15:06:23Z | MEMBER | choosing default values is hard and always some kind of a tradeoff. In general we should strive to choose a default that is useful to most users (but how do you measure "useful to most users"?), and if that is not the case for a particular use case it should be configurable. I agree that having to remember to add the For this particular setting I think the idea for the current value was that printing a lot of variables is slow and, most importantly, that the Thoughts, @pydata/xarray? Disabling the restriction should be possible (but again, not the default), maybe |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Increase default `display_max_rows` 931591247 |
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