issue_comments
2 rows where user = 9097307 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
user 1
- brian-rose · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
341520352 | https://github.com/pydata/xarray/pull/1643#issuecomment-341520352 | https://api.github.com/repos/pydata/xarray/issues/1643 | MDEyOklzc3VlQ29tbWVudDM0MTUyMDM1Mg== | brian-rose 9097307 | 2017-11-02T18:42:38Z | 2017-11-02T18:42:38Z | CONTRIBUTOR | I'm happy to see this too!
I raised this way back in https://github.com/pydata/xarray/issues/687, but at the time the consensus was that |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Deprecate Dataset.T as an alias for Dataset.transpose() 267339197 | |
167708699 | https://github.com/pydata/xarray/issues/687#issuecomment-167708699 | https://api.github.com/repos/pydata/xarray/issues/687 | MDEyOklzc3VlQ29tbWVudDE2NzcwODY5OQ== | brian-rose 9097307 | 2015-12-29T03:09:47Z | 2015-12-29T03:09:47Z | CONTRIBUTOR | Brilliant, somehow I missed the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Dataset.T property creates conflict with data named 'T' 124129804 |
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]);
issue 2