issue_comments

Table actions

1 row where issue = 441192361 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

issue 1

  • Implicit conversion from int to float tampers with values when int is not representable as float · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
490127033 https://github.com/pydata/xarray/issues/2945#issuecomment-490127033 https://api.github.com/repos/pydata/xarray/issues/2945 MDEyOklzc3VlQ29tbWVudDQ5MDEyNzAzMw== shoyer 1217238 2019-05-07T15:23:51Z 2019-05-07T15:23:51Z MEMBER

You can avoid this by setting a other in where explicitly, e.g., ds.where(ds.var1 == val, other=-1).

Unfortunately I don't see any good way to fix this short of NumPy support for an integer dtype with missing values. If we disabled automatic casting from integer to float values when NaNs could be introduced, then lots of operations would just fail instead.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implicit conversion from int to float tampers with values when int is not representable as float 441192361

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