home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where issue = 59323055 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

  • shoyer 2
  • jhamman 1

issue 1

  • Alternatives to virtual variables in the form "time.season"? · 3 ✖

author_association 1

  • MEMBER 3
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
76866830 https://github.com/pydata/xarray/issues/345#issuecomment-76866830 https://api.github.com/repos/pydata/xarray/issues/345 MDEyOklzc3VlQ29tbWVudDc2ODY2ODMw shoyer 1217238 2015-03-03T01:10:12Z 2015-03-03T01:10:12Z MEMBER

:)

@jhamman FWIW, I think we've one bug fix and a few documentation tweaks (including yours) away from being ready to release v0.4.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Alternatives to virtual variables in the form "time.season"? 59323055
76865700 https://github.com/pydata/xarray/issues/345#issuecomment-76865700 https://api.github.com/repos/pydata/xarray/issues/345 MDEyOklzc3VlQ29tbWVudDc2ODY1NzAw jhamman 2443309 2015-03-03T01:00:36Z 2015-03-03T01:00:36Z MEMBER

Looks good @shoyer. This is what I would have suggested.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Alternatives to virtual variables in the form "time.season"? 59323055
76781257 https://github.com/pydata/xarray/issues/345#issuecomment-76781257 https://api.github.com/repos/pydata/xarray/issues/345 MDEyOklzc3VlQ29tbWVudDc2NzgxMjU3 shoyer 1217238 2015-03-02T18:58:42Z 2015-03-02T18:58:42Z MEMBER

After some contemplation, I think it's actually OK to switch to the result of ds['time.season'] to being a DataArray with the name 'season'. The use of . is already an indicator that something special is going on. I'll switch this for v0.4.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Alternatives to virtual variables in the form "time.season"? 59323055

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