issue_comments

Table actions

1 row where user = 7462311 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

  • earlew · 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
76500617 https://github.com/pydata/xarray/issues/343#issuecomment-76500617 https://api.github.com/repos/pydata/xarray/issues/343 MDEyOklzc3VlQ29tbWVudDc2NTAwNjE3 earlew 7462311 2015-02-28T01:02:27Z 2015-02-28T01:02:27Z NONE

Points taken. Thanks for responding so quickly. I didn't realize that Pandas does something similar. I understand that the default behavior of NumPy/Python is to pass by reference (assignment) but I didn't realize that this rule applies even when converting an object from one type to another. Now that I have checked, np.ma.masked_array also uses a reference to the input data by default (however, it also provides the option for creating a copy).

In the API reference for DataArray, it probably wouldn't hurt to say that the input data is not copied by default and that a reference is used instead. I guess making note of this would only benefit less experienced users like myself, but it would be appreciated. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   DataArrays initialized with the same data behave like views of each other 59308959

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