issue_comments

Table actions

1 row where issue = 103966239 and user = 1217238 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

  • shoyer · 1 ✖

issue 1

  • Fixes for complex numbers · 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
137178766 https://github.com/pydata/xarray/pull/554#issuecomment-137178766 https://api.github.com/repos/pydata/xarray/issues/554 MDEyOklzc3VlQ29tbWVudDEzNzE3ODc2Ng== shoyer 1217238 2015-09-02T17:25:08Z 2015-09-02T17:25:08Z MEMBER

One question still: what is the point of applying .real or .imag to dataset ? As far as I understand xray.Dataset might be inhomogeneous (a mix of non homogeneous datatypes). It doe make sense for xray.Dataarray though.

If every data variable in your Dataset has numeric values, .real and .imag are perfectly well defined. If not, you'll get an error message when you try to use them. This is similar to the case for other operations that only work on numbers (e.g., binary arithmetic).

My two cents is that .real and .imag would also be appropriate for pandas.DataFrame, even though they only make sense for certain dtypes.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fixes for complex numbers 103966239

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