issue_comments

Table actions

1 row where author_association = "NONE", issue = 841012076 and user = 5567953 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • hamiddashti · 1 ✖

issue 1

  • Losing data when add a raster to a dataset · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
832793635 https://github.com/pydata/xarray/issues/5075#issuecomment-832793635 https://api.github.com/repos/pydata/xarray/issues/5075 MDEyOklzc3VlQ29tbWVudDgzMjc5MzYzNQ== hamiddashti 5567953 2021-05-05T15:40:30Z 2021-05-05T15:40:30Z NONE

A "close enough" option can take care of issues such as in xarray.where in situations where the coordinates are very close but not exactly matched (here) (e.g. due to Geotif roudning, here ) . 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Losing data when add a raster to a dataset 841012076

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);