issue_comments

Table actions

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

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association

user 1

  • shoyer · 1 ✖

issue 1

  • Applying the stack function to DataArray resulted in data type changes on coordinates · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
465443580 https://github.com/pydata/xarray/issues/2774#issuecomment-465443580 https://api.github.com/repos/pydata/xarray/issues/2774 MDEyOklzc3VlQ29tbWVudDQ2NTQ0MzU4MA== shoyer 1217238 2019-02-20T06:30:50Z 2019-02-20T06:30:50Z MEMBER

That said, xarray could keep around a float32 array along with the float64 index. This is likely to be possible soon as part of the “explicit indexes” refactor (https://github.com/pydata/xarray/issues/1603).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Applying the stack function to DataArray resulted in data type changes on coordinates 411650684

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