issue_comments

Table actions

5 rows where issue = 72145600 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

issue 1

  • millisecond and microseconds support · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
97896826 https://github.com/pydata/xarray/issues/406#issuecomment-97896826 https://api.github.com/repos/pydata/xarray/issues/406 MDEyOklzc3VlQ29tbWVudDk3ODk2ODI2 shoyer 1217238 2015-04-30T17:51:10Z 2015-04-30T17:51:10Z MEMBER

There's also leap seconds, and I'm pretty sure that none of the underlying libraries here handle those properly.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   millisecond and microseconds support 72145600
97896201 https://github.com/pydata/xarray/issues/406#issuecomment-97896201 https://api.github.com/repos/pydata/xarray/issues/406 MDEyOklzc3VlQ29tbWVudDk3ODk2MjAx jhamman 2443309 2015-04-30T17:48:47Z 2015-04-30T17:48:47Z MEMBER

My thoughts exactly. The original post mentioned netcdftime so I thought it would be beneficial to point that out. For standard calendards using Python/Numpy datetime objects, microsecond precision is preserved.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   millisecond and microseconds support 72145600
97895435 https://github.com/pydata/xarray/issues/406#issuecomment-97895435 https://api.github.com/repos/pydata/xarray/issues/406 MDEyOklzc3VlQ29tbWVudDk3ODk1NDM1 shoyer 1217238 2015-04-30T17:46:27Z 2015-04-30T17:46:27Z MEMBER

We use numpy's datetime64 machinery instead of netcdftime when possible, so at least for the standard/gregorian calendar this might actually be OK.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   millisecond and microseconds support 72145600
97892365 https://github.com/pydata/xarray/issues/406#issuecomment-97892365 https://api.github.com/repos/pydata/xarray/issues/406 MDEyOklzc3VlQ29tbWVudDk3ODkyMzY1 jhamman 2443309 2015-04-30T17:38:15Z 2015-04-30T17:38:15Z MEMBER

As a small side note, netcdf4-python doesn't exactly support microseconds. There is a known precision issue that ends up giving netcdftime a minimum time precision of seconds: https://github.com/Unidata/netcdf4-python/issues/321

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   millisecond and microseconds support 72145600
97889390 https://github.com/pydata/xarray/issues/406#issuecomment-97889390 https://api.github.com/repos/pydata/xarray/issues/406 MDEyOklzc3VlQ29tbWVudDk3ODg5Mzkw shoyer 1217238 2015-04-30T17:30:21Z 2015-04-30T17:30:21Z MEMBER

Sure, this is pretty easy to add. Should make it into the next release.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   millisecond and microseconds support 72145600

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