home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where issue = 29067976 and user = 514053 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

  • akleeman · 2 ✖

issue 1

  • Ensure decoding as datetime64[ns] · 2 ✖

author_association 1

  • CONTRIBUTOR 2
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
37503963 https://github.com/pydata/xarray/pull/59#issuecomment-37503963 https://api.github.com/repos/pydata/xarray/issues/59 MDEyOklzc3VlQ29tbWVudDM3NTAzOTYz akleeman 514053 2014-03-13T06:32:59Z 2014-03-13T06:32:59Z CONTRIBUTOR

Yeah, does seem that way. Unfortunately that makes comparison with datetime objects a bit awkward. Perhaps we should include a to_datetime() the way pandas does? Certainly, it would be convenient to be able to do comparisons such as:

ds['time'].data > datetime.datetime(2014, 01, 01)

This is definitely not high priority though.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Ensure decoding as datetime64[ns] 29067976
37433623 https://github.com/pydata/xarray/pull/59#issuecomment-37433623 https://api.github.com/repos/pydata/xarray/issues/59 MDEyOklzc3VlQ29tbWVudDM3NDMzNjIz akleeman 514053 2014-03-12T16:55:52Z 2014-03-12T16:55:52Z CONTRIBUTOR

I'll go ahead and merge this in to fix the bug ... but I wonder if there is any way we can avoid using np.datetime64 objects. They seem under-developed / broken.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Ensure decoding as datetime64[ns] 29067976

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 640.993ms · About: xarray-datasette