issue_comments

Table actions

1 row where issue = 1473329967 and user = 2448579 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

  • dcherian · 1 ✖

issue 1

  • Coordinate variable gains coordinate on subset · 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
1338119644 https://github.com/pydata/xarray/issues/7350#issuecomment-1338119644 https://api.github.com/repos/pydata/xarray/issues/7350 IC_kwDOAMm_X85PwhXc dcherian 2448579 2022-12-05T20:22:43Z 2022-12-05T20:25:31Z MEMBER

One way to fix this would be to never associate non-dim coords when creating a DataArray for a dimension coordinate. But I think it may be better to encourage users to use .variable instead.

The behavior I'd advocate for is that a subsetting/selection operation should never add new coordinates that weren't previously present.

What do you mean by "previously present"? We'd have to track state of some sort, which doesn't seem ideal. Alternatively, the user could use .sel(time=[0]). That would preserve the identity of time as a dimension coordinate (of size 1), and it would not get associated when extracting lat

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Coordinate variable gains coordinate on subset 1473329967

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