home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

4 rows where author_association = "MEMBER" and issue = 29008494 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 4

issue 1

  • Allow datetime.timedelta coordinates. · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
58556580 https://github.com/pydata/xarray/issues/55#issuecomment-58556580 https://api.github.com/repos/pydata/xarray/issues/55 MDEyOklzc3VlQ29tbWVudDU4NTU2NTgw shoyer 1217238 2014-10-09T18:38:16Z 2014-10-09T18:38:16Z MEMBER

pandas.TimedeltaIndex will finally arrive in the next version of pandas. It would be nice to support it with properly encoding/decoding.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Allow datetime.timedelta coordinates. 29008494
43283157 https://github.com/pydata/xarray/issues/55#issuecomment-43283157 https://api.github.com/repos/pydata/xarray/issues/55 MDEyOklzc3VlQ29tbWVudDQzMjgzMTU3 shoyer 1217238 2014-05-16T00:45:12Z 2014-05-16T00:45:12Z MEMBER

For a full solution, it would be great if pandas included a TimeDeltaIndex so we don't have to use an index with dtype=object. Here is the pandas issue: pydata/pandas#3009

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Allow datetime.timedelta coordinates. 29008494
37082749 https://github.com/pydata/xarray/issues/55#issuecomment-37082749 https://api.github.com/repos/pydata/xarray/issues/55 MDEyOklzc3VlQ29tbWVudDM3MDgyNzQ5 shoyer 1217238 2014-03-08T00:37:15Z 2014-03-08T00:37:15Z MEMBER

It would be useful, however, to have automatic encoding/decoding of such variables to NETCDF.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Allow datetime.timedelta coordinates. 29008494
37082695 https://github.com/pydata/xarray/issues/55#issuecomment-37082695 https://api.github.com/repos/pydata/xarray/issues/55 MDEyOklzc3VlQ29tbWVudDM3MDgyNjk1 shoyer 1217238 2014-03-08T00:35:48Z 2014-03-08T00:35:48Z MEMBER

In fact, I have a fix for this in #54. See utils.safe_cast_to_index.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Allow datetime.timedelta coordinates. 29008494

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]);
Powered by Datasette · Queries took 12.4ms · About: xarray-datasette