issue_comments

Table actions

3 rows where issue = 46756880 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 · 3 ✖

issue 1

  • can't use datetime or pandas datetime to index time dimension · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
60707841 https://github.com/pydata/xarray/issues/267#issuecomment-60707841 https://api.github.com/repos/pydata/xarray/issues/267 MDEyOklzc3VlQ29tbWVudDYwNzA3ODQx shoyer 1217238 2014-10-28T04:15:04Z 2014-10-28T04:15:04Z MEMBER

Closing this, but please let me know if you notice any other apparent inconsistencies.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   can't use datetime or pandas datetime to index time dimension 46756880
60426317 https://github.com/pydata/xarray/issues/267#issuecomment-60426317 https://api.github.com/repos/pydata/xarray/issues/267 MDEyOklzc3VlQ29tbWVudDYwNDI2MzE3 shoyer 1217238 2014-10-24T18:06:23Z 2014-10-24T18:06:23Z MEMBER

We pass off all label interpretation to pandas, so this discussion is really about what pandas does. The partial string selection is indeed a pandas feature: http://pandas.pydata.org/pandas-docs/stable/timeseries.html#datetimeindex-partial-string-indexing

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   can't use datetime or pandas datetime to index time dimension 46756880
60417045 https://github.com/pydata/xarray/issues/267#issuecomment-60417045 https://api.github.com/repos/pydata/xarray/issues/267 MDEyOklzc3VlQ29tbWVudDYwNDE3MDQ1 shoyer 1217238 2014-10-24T17:01:46Z 2014-10-24T17:01:46Z MEMBER

Try supplying the exact date and time.e.g, datetime(2013, 1, 1, 11, 15) (I think that's right), or doing a slice, e.g., c.sel(time=slice(datetime(2013, 1, 1), datetime(2013, 1, 2))).

This should definitely work but pandas (reasonably) assumes that datetime objects refer to particular instants in time, unlike strings, which are less precise.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   can't use datetime or pandas datetime to index time dimension 46756880

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