home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where issue = 139956689 and user = 2443309 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • jhamman · 2 ✖

issue 1

  • Time limitation (between years 1678 and 2262) restrictive to climate community · 2 ✖

author_association 1

  • MEMBER 2
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
219928912 https://github.com/pydata/xarray/issues/789#issuecomment-219928912 https://api.github.com/repos/pydata/xarray/issues/789 MDEyOklzc3VlQ29tbWVudDIxOTkyODkxMg== jhamman 2443309 2016-05-18T05:29:20Z 2016-05-18T05:29:20Z MEMBER

@brews - I think this issue (https://github.com/pydata/pandas/issues/7307) covers the main gist of what we're talking about here.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Time limitation (between years 1678 and 2262) restrictive to climate community 139956689
195031692 https://github.com/pydata/xarray/issues/789#issuecomment-195031692 https://api.github.com/repos/pydata/xarray/issues/789 MDEyOklzc3VlQ29tbWVudDE5NTAzMTY5Mg== jhamman 2443309 2016-03-10T20:23:26Z 2016-03-10T20:23:26Z MEMBER

This might make slightly more sense in a related but distinct project to xarray.

@shoyer - are you thinking xarray would fall back to a CustomDatetimeIndex for non-standard calendars?

I actually don't think it would be all that hard to do this. @jswhit's netcdftime module is at least a good starting point. There's a lot to build on in netcdftime and pandas.tseries.index. I'd actually say this should be targeted at Pandas (probably as a side project) rather than xarray. Ultimately, it would be nice to be able to move timeseries back and forth without any hassle.

I'd be happy to help pull this together, although, I won't be able to make significant contributions until the summer. Is anyone chomping at the bit to work on something like this?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Time limitation (between years 1678 and 2262) restrictive to climate community 139956689

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 4158.714ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows