issue_comments

Table actions

1 row where issue = 156073920 and user = 2443309 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: author_association, issue

user 1

  • jhamman · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
220862100 https://github.com/pydata/xarray/issues/853#issuecomment-220862100 https://api.github.com/repos/pydata/xarray/issues/853 MDEyOklzc3VlQ29tbWVudDIyMDg2MjEwMA== jhamman 2443309 2016-05-22T23:03:25Z 2016-05-22T23:03:25Z MEMBER

@MaximilianR - pytest is great. I prefer its test syntax to the standard UnitTest framework. We can write tests using either right now. Is your question about whether or not we want to start moving our syntax over?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   TST: Py.test 156073920

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