issue_comments

Table actions

4 rows where author_association = "MEMBER" and issue = 1390999159 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

issue 1

  • Fix to_index(): return multiindex level as single index · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1276250502 https://github.com/pydata/xarray/pull/7105#issuecomment-1276250502 https://api.github.com/repos/pydata/xarray/issues/7105 IC_kwDOAMm_X85MEgmG dcherian 2448579 2022-10-12T14:12:43Z 2022-10-12T14:12:43Z MEMBER

Thanks @benbovy 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix to_index(): return multiindex level as single index 1390999159
1271519573 https://github.com/pydata/xarray/pull/7105#issuecomment-1271519573 https://api.github.com/repos/pydata/xarray/issues/7105 IC_kwDOAMm_X85LydlV benbovy 4160723 2022-10-07T12:20:49Z 2022-10-07T12:20:49Z MEMBER

Tests should be ok now, although this is not a super clean workaround. IndexVariable still needs some more refactoring anyway.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix to_index(): return multiindex level as single index 1390999159
1266068474 https://github.com/pydata/xarray/pull/7105#issuecomment-1266068474 https://api.github.com/repos/pydata/xarray/issues/7105 IC_kwDOAMm_X85Ldqv6 benbovy 4160723 2022-10-03T21:22:42Z 2022-10-03T21:22:42Z MEMBER

Yes I agree it would be nice if we can roll back this breaking change. However, it really conflicts with .xindexes that returns the same index instance for each of its corresponding coordinate. This roll back seems to mostly break things where we need to be smart while handling multi-index coordinates passed to DataArray / Dataset constructors. This might be tricky to solve. It would probably be easier to do it after #6392.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix to_index(): return multiindex level as single index 1390999159
1266025233 https://github.com/pydata/xarray/pull/7105#issuecomment-1266025233 https://api.github.com/repos/pydata/xarray/issues/7105 IC_kwDOAMm_X85LdgMR dcherian 2448579 2022-10-03T20:43:50Z 2022-10-03T20:43:50Z MEMBER

I like this fix in general: we fix the backwards incompatible change and work to remove MultiIndex special cases separately.

Though this PR seems to have broken a lot of things :)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix to_index(): return multiindex level as single index 1390999159

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