issue_comments

Table actions

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

  • shoyer · 1 ✖

issue 1

  • Whether should we follow pandas or numpy if they have different API? · 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
362943502 https://github.com/pydata/xarray/issues/1886#issuecomment-362943502 https://api.github.com/repos/pydata/xarray/issues/1886 MDEyOklzc3VlQ29tbWVudDM2Mjk0MzUwMg== shoyer 1217238 2018-02-04T22:00:05Z 2018-02-04T22:00:05Z MEMBER

I think a distinction between argmin/idxmin is useful -- and it seems that pandas is likely to restore this in the future as well.

The difference between ddof=0 and ddof=1 has never mattered to me. I suppose it probably does make more sense for us to follow pandas here (it's what we usually do), but I don't know if it's worth the trouble of changing it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Whether should we follow pandas or numpy if they have different API? 294182366

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