home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where issue = 148771214 and user = 4295853 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

  • pwolfram · 2 ✖

issue 1

  • Storing history of xarray operations · 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
210710788 https://github.com/pydata/xarray/issues/826#issuecomment-210710788 https://api.github.com/repos/pydata/xarray/issues/826 MDEyOklzc3VlQ29tbWVudDIxMDcxMDc4OA== pwolfram 4295853 2016-04-16T01:56:41Z 2016-04-16T01:56:41Z CONTRIBUTOR

Thanks @shoyer! I think after this discussion that this is something we should handle within our own wrapper. There does not seem to be a clean one size fits all solution warranting inclusion in xarray, unless I'm mistaken. If so, I hope someone chimes in to correct me.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Storing history of xarray operations 148771214
210683210 https://github.com/pydata/xarray/issues/826#issuecomment-210683210 https://api.github.com/repos/pydata/xarray/issues/826 MDEyOklzc3VlQ29tbWVudDIxMDY4MzIxMA== pwolfram 4295853 2016-04-15T23:32:03Z 2016-04-15T23:32:03Z CONTRIBUTOR

Thanks @shoyer. Is the fundamental issue code boat or is the concern essentially storing a history that may not be useful? The reason I ask is because we could capture all method operation names and sore them to a log. You are right that this could get really messy and potentially meaningless as a result.

However, what about storing the text related to the calling script used to call to-netcdf? Perhaps that may work in terms of enhanced documentation. I think there could be some utility to be gained here, especially in team environments.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Storing history of xarray operations 148771214

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