issue_comments

Table actions

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

issue 1

  • API: are indexes public API? · 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
255254094 https://github.com/pydata/xarray/issues/1054#issuecomment-255254094 https://api.github.com/repos/pydata/xarray/issues/1054 MDEyOklzc3VlQ29tbWVudDI1NTI1NDA5NA== shoyer 1217238 2016-10-20T23:19:12Z 2016-10-20T23:19:12Z MEMBER

Yes, DataArray.indexes is public API, as is the DataArray.to_index() method. If it's not listed in the API docs, that should be fixed. (It does look like it's missing.)

It is possible that at some point in the future we may allow alternative indexes, e.g., stored on disk or over a network. But I have no such plans and in any case this would certainly require explicitly opting in.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   API: are indexes public API? 184327428

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