issue_comments

Table actions

1 row where issue = 295621576 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

  • Vectorized indexing with cache=False · 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
364294048 https://github.com/pydata/xarray/issues/1897#issuecomment-364294048 https://api.github.com/repos/pydata/xarray/issues/1897 MDEyOklzc3VlQ29tbWVudDM2NDI5NDA0OA== shoyer 1217238 2018-02-09T00:20:16Z 2018-02-09T00:20:16Z MEMBER

In the current version of LazilyIndexArray, we combined successive indexers into a single indexer, e.g., array[k1][k2] -> array[k3] without evaluating the array.

Someone would either need to think through how to do this for successive VectorizedIndexer objects (all other indexers can be converted in VectorizedIndexer objects if needed). Or we could switch LazilyIndexedArray to store a chain of successive indexing operations, but that would potentially have non-desirable performance implications.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Vectorized indexing with cache=False 295621576

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