issue_comments

Table actions

1 row where issue = 231838537 and user = 6815844 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

These facets timed out: issue

user 1

  • fujiisoup · 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
304488264 https://github.com/pydata/xarray/issues/1431#issuecomment-304488264 https://api.github.com/repos/pydata/xarray/issues/1431 MDEyOklzc3VlQ29tbWVudDMwNDQ4ODI2NA== fujiisoup 6815844 2017-05-28T02:16:05Z 2017-05-28T03:42:13Z MEMBER

Hi @d-chambers

I am currently working for more consistent MultiIndex behaviour in #1426 . I will take a look also for stack-unstack behavior.

 
{
    "total_count": 2,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 1,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   inconsistent behavior in stack/unstack along one dimension 231838537

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