issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 314241348 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: issue

user 1

  • shoyer · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
381278786 https://github.com/pydata/xarray/issues/2056#issuecomment-381278786 https://api.github.com/repos/pydata/xarray/issues/2056 MDEyOklzc3VlQ29tbWVudDM4MTI3ODc4Ng== shoyer 1217238 2018-04-13T22:50:56Z 2018-04-13T22:50:56Z MEMBER

Hmm. This warning message is slightly unfortunate indeed.

Currently we retain the coords, but discard attrs. That seems arbitrary?

Agreed!

I don't have a strong view. If you think that Foo(foo) should always return foo (which is often the case in pandas), then we should retain the full object.

Yes, we could defensibly go either way here.

Generally, I don't think this is an important invariant, and it certainly doesn't make sense for every type. But maybe it does make sense for Dataset, given that we do do so for DataArray: https://github.com/pydata/xarray/blob/a9d1f3a36229636f0d519eb36a8d4a7c91f6e1cd/xarray/core/dataarray.py#L205-L223

(But to be clear, this wasn't a terribly careful design decision for DataArray, either.)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Warning on supplying a Dataset to the Dataset constructor 314241348

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