issue_comments

Table actions

1 row where issue = 866530388 and user = 14808389 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

  • keewis · 1 ✖

issue 1

  • When try to assign a pd.MultiIndex to the coords, the behavior is different between "Dimension coordinate" and "Non-dimension coordinate" · 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
826092332 https://github.com/pydata/xarray/issues/5214#issuecomment-826092332 https://api.github.com/repos/pydata/xarray/issues/5214 MDEyOklzc3VlQ29tbWVudDgyNjA5MjMzMg== keewis 14808389 2021-04-24T13:21:47Z 2021-04-24T13:21:47Z MEMBER

right now, the main difference between dimension and non-dimension coordinates is exactly that: dimension coordinates have a index while non-dimension coordinates don't. That means that before assigning the index to non-dimension coordinates it is converted to numpy.

@benbovy is currently working on changing the data model, which will probably allow the behavior you're expecting. See #1603 and #4979.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   When try to assign a pd.MultiIndex to the coords, the behavior is different between "Dimension coordinate" and "Non-dimension coordinate" 866530388

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