issue_comments

Table actions

1 row where author_association = "CONTRIBUTOR" and issue = 40225000 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

  • Get ride of "noncoordinates" as a name? · 1 ✖

author_association 1

  • CONTRIBUTOR · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
54560323 https://github.com/pydata/xarray/issues/212#issuecomment-54560323 https://api.github.com/repos/pydata/xarray/issues/212 MDEyOklzc3VlQ29tbWVudDU0NTYwMzIz akleeman 514053 2014-09-04T23:35:26Z 2014-09-04T23:35:26Z CONTRIBUTOR

I personally am not familiar with pandas.Block objects, so I find the name uniformative. That combined with the fact that renaming Variable to Block would break alignment with netCDF naming conventions (so confuse users coming from that background) makes me hesitant about the change. I think I'd be more excited about finding a better name for noncoordinates (fields? ) instead of renaming variables (which would also cause non-backwards compatibility)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Get ride of "noncoordinates" as a name? 40225000

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