issue_comments

Table actions

1 row where issue = 170305429 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
238745229 https://github.com/pydata/xarray/issues/957#issuecomment-238745229 https://api.github.com/repos/pydata/xarray/issues/957 MDEyOklzc3VlQ29tbWVudDIzODc0NTIyOQ== shoyer 1217238 2016-08-10T01:56:22Z 2016-08-10T01:56:22Z MEMBER

I would be interested to know if registering an accessor works for you, which was designed for exactly this sort of use case: http://xarray.pydata.org/en/stable/internals.html#extending-xarray

The reason why I chose not to just use the qualified name is that xarray.core.dataset.Dataset is a little long, and also points users in the direction of private API.

But I'd be happy to use qualified names for subclasses not builtin to xarray. Currently you can find this logic in dataset_repr and array_repr at the bottom of core/formatting.py. You'd just need to write a helper function to calculate the class name rather than our current use of u'<xarray.%s>' % type(ds).__name__. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   BUG: Repr on inherited classes is incorrect 170305429

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]);