issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 316540429 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

  • recommend xr.Dataset.from_dataframe(df) instead of xr.Dataset(df) for… · 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
383355977 https://github.com/pydata/xarray/pull/2073#issuecomment-383355977 https://api.github.com/repos/pydata/xarray/issues/2073 MDEyOklzc3VlQ29tbWVudDM4MzM1NTk3Nw== shoyer 1217238 2018-04-22T05:10:17Z 2018-04-22T05:10:17Z MEMBER

I agree that from_dataframe should be preferred -- which is exactly why we mention in first on this doc page.

I'm not sure this change makes sense, since the leading paragraph introduces this example with "Both the DataArray and Dataset constructors..."

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   recommend xr.Dataset.from_dataframe(df) instead of xr.Dataset(df) for… 316540429

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