issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 185441216 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
256410357 https://github.com/pydata/xarray/issues/1062#issuecomment-256410357 https://api.github.com/repos/pydata/xarray/issues/1062 MDEyOklzc3VlQ29tbWVudDI1NjQxMDM1Nw== shoyer 1217238 2016-10-26T16:52:39Z 2016-10-26T16:52:39Z MEMBER

Indeed, NumPy converts these units inconsistently with Udunits:

```

np.timedelta64(1, 'Y').astype('timedelta64[D]') numpy.timedelta64(365,'D') ```

We currently convert all datetime arrays to ns resolution (for pandas compatibility), which means this would give possibly broken results.

But honestly, we haven't looked into this very much. If this would be a uniform improvement over the current state then it's worth considering.

CC @jhamman 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add remaining date units to conventions.py 185441216

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