issue_comments
1 row where issue = 608536405 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Subset from conditional coordinates · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
621379267 | https://github.com/pydata/xarray/issues/4013#issuecomment-621379267 | https://api.github.com/repos/pydata/xarray/issues/4013 | MDEyOklzc3VlQ29tbWVudDYyMTM3OTI2Nw== | keewis 14808389 | 2020-04-29T18:17:12Z | 2020-04-29T18:17:12Z | MEMBER | take a look at https://xarray.pydata.org/en/stable/#get-in-touch where a few options are listed. I'm not a active user of SO / SE so I can't comment on that, but I think it is fine to ask questions like this one using the issue tracker. Also, thanks for reaching out about the examples. I agree we should have descriptions on what each of them is trying to achieve, and we should also think about linking to the relevant section in the narrative documentation. In this case, that would be https://xarray.pydata.org/en/stable/indexing.html#masking-with-where |
{ "total_count": 3, "+1": 3, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Subset from conditional coordinates 608536405 |
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