issue_comments

Table actions

2 rows where issue = 169276671 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 · 2 ✖

issue 1

  • Don't convert time data to timedelta by default · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
237654592 https://github.com/pydata/xarray/pull/940#issuecomment-237654592 https://api.github.com/repos/pydata/xarray/issues/940 MDEyOklzc3VlQ29tbWVudDIzNzY1NDU5Mg== shoyer 1217238 2016-08-04T19:15:38Z 2016-08-04T19:15:38Z MEMBER

It might be worth querying the mailing list for more opinions here.

If the main issue is plotting, you could try fixing that upstream, too! https://github.com/pydata/pandas/issues/8711

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't convert time data to timedelta by default 169276671
237614917 https://github.com/pydata/xarray/pull/940#issuecomment-237614917 https://api.github.com/repos/pydata/xarray/issues/940 MDEyOklzc3VlQ29tbWVudDIzNzYxNDkxNw== shoyer 1217238 2016-08-04T16:56:07Z 2016-08-04T16:56:07Z MEMBER

Decoding time units into timedelta64 is useful if you want to be able to use them for arithmetic with datetimes. I agree that this is not always the most useful currently because, e.g., plotting doesn't work very well, and time deltas in nanoseconds are difficult to interpret. Still I'm somewhat reluctant to change the default here.

Either way, we will definitely need to support the original decode_times keyword argument for now (with a deprecation warning) so there is a smooth transition.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't convert time data to timedelta by default 169276671

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