issue_comments

Table actions

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

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • shoyer · 1 ✖

issue 1

  • Flexible indexes: how to handle possible dimension vs. coordinate name conflicts? · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
906792475 https://github.com/pydata/xarray/issues/5738#issuecomment-906792475 https://api.github.com/repos/pydata/xarray/issues/5738 IC_kwDOAMm_X842DI4b shoyer 1217238 2021-08-26T22:46:19Z 2021-08-26T22:46:19Z MEMBER

In the long term, I think we want to eliminate any requirements in Xarray's data model about what variables names are OK.

In particular: 1. We want to allow a coordinate named "foo" with different dimensions than ("foo",), in order to support reading all possible netCDF files into xarray. 2. We want to allow indexing with coordinates that are not dimensions.

With this second change in particular, it should not be a problem to have a multi-index level with the same name as a dimension.

It is true that this change will introduce an inconsistency between appropriate keys for use with sel (indexed coordinates) and isel (dimensions). But I think this is basically inevitable.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Flexible indexes: how to handle possible dimension vs. coordinate name conflicts? 979316661

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