issue_comments

Table actions

2 rows where author_association = "MEMBER" and issue = 230158616 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

issue 1

  • Save arbitrary Python objects to netCDF · 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
302897807 https://github.com/pydata/xarray/issues/1415#issuecomment-302897807 https://api.github.com/repos/pydata/xarray/issues/1415 MDEyOklzc3VlQ29tbWVudDMwMjg5NzgwNw== shoyer 1217238 2017-05-20T20:46:55Z 2017-05-20T20:46:55Z MEMBER

Sure, there's no harm in asking. My guess is that this isn't a good fit, but I'm not entirely sure.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Save arbitrary Python objects to netCDF 230158616
302879988 https://github.com/pydata/xarray/issues/1415#issuecomment-302879988 https://api.github.com/repos/pydata/xarray/issues/1415 MDEyOklzc3VlQ29tbWVudDMwMjg3OTk4OA== shoyer 1217238 2017-05-20T15:28:55Z 2017-05-20T15:28:55Z MEMBER

I would be OK with this if it required explicitly setting a keyword argument, e.g., ds.to_netcdf(..., allow_pickle=True) and xarray.open_dataset(..., allow_pickle=True). This could be hooked into xarray's existing coding/decoding layer in a relatively straightforward fashion: see ensure_dtype_not_object for where this is caught in the current code. (We would also need something at a lower level in the netCDF4 specific reader/writer to handle uint8 VLType.)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Save arbitrary Python objects to netCDF 230158616

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