issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 338662554 and user = 2443309 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_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
403172343 https://github.com/pydata/xarray/issues/2269#issuecomment-403172343 https://api.github.com/repos/pydata/xarray/issues/2269 MDEyOklzc3VlQ29tbWVudDQwMzE3MjM0Mw== jhamman 2443309 2018-07-06T23:52:30Z 2018-07-06T23:52:30Z MEMBER

My 2 cents. I would be reluctant to find this in Xarray anytime soon. This just seems like its going to be a hard thing to maintain. Perhaps, after the data model and api have really stabilized, this would make sense, but it strikes me as something that is going to be more work than its worth to maintain. Afterall, we can rountrip xarray datasets to a number of stable file formats.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A special function for unpickling old xarray object? 338662554

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