issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 235224055 and user = 10194086 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

  • mathause · 1 ✖

issue 1

  • time.units truncated when saving to_netcdf · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
308105236 https://github.com/pydata/xarray/issues/1449#issuecomment-308105236 https://api.github.com/repos/pydata/xarray/issues/1449 MDEyOklzc3VlQ29tbWVudDMwODEwNTIzNg== mathause 10194086 2017-06-13T12:50:38Z 2017-06-13T12:50:38Z MEMBER

Well, not specifying the time would conform to the CF conventions... (http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html#time-coordinate), so this might be an issue in panoply.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   time.units truncated when saving to_netcdf 235224055

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