issue_comments

Table actions

1 row where issue = 89866276 and user = 141709 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

  • sjpfenninger · 1 ✖

issue 1

  • Display datetime64 arrays without showing local timezones · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
212940728 https://github.com/pydata/xarray/issues/439#issuecomment-212940728 https://api.github.com/repos/pydata/xarray/issues/439 MDEyOklzc3VlQ29tbWVudDIxMjk0MDcyOA== sjpfenninger 141709 2016-04-21T14:23:54Z 2016-04-21T14:23:54Z CONTRIBUTOR

Would it not make sense to use a pandas.DatetimeIndex instead of pure-numpy datetimes? It seems that DatetimeIndex already solves lots of the weirdness in the underlying numpy datetime objects and adds a bunch of useful functionality for things like groupby operations.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Display datetime64 arrays without showing local timezones 89866276

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