issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 787847449 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • keewis · 3 ✖

issue 1

  • Error when supplying a tuple of dimensions to DataArray.sortby() · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
859802038 https://github.com/pydata/xarray/issues/4821#issuecomment-859802038 https://api.github.com/repos/pydata/xarray/issues/4821 MDEyOklzc3VlQ29tbWVudDg1OTgwMjAzOA== keewis 14808389 2021-06-11T19:45:26Z 2021-06-11T19:45:26Z MEMBER

here's an example: python In [2]: xr.Dataset({"a": ([("a", "b")], [1])}) Out[2]: <xarray.Dataset> Dimensions: (('a', 'b'): 1) Dimensions without coordinates: ('a', 'b') Data variables: a (('a', 'b')) int64 1

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Error when supplying a tuple of dimensions to DataArray.sortby() 787847449
766234825 https://github.com/pydata/xarray/issues/4821#issuecomment-766234825 https://api.github.com/repos/pydata/xarray/issues/4821 MDEyOklzc3VlQ29tbWVudDc2NjIzNDgyNQ== keewis 14808389 2021-01-23T23:50:40Z 2021-01-23T23:50:53Z MEMBER

All of these options are breaking changes so we would probably have to go through a deprecation cycle. 1 might be the most consistent and least confusing, but if we want to keep the current behavior we could require wrapping a tuple in another sequence to access dimension names.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Error when supplying a tuple of dimensions to DataArray.sortby() 787847449
762523614 https://github.com/pydata/xarray/issues/4821#issuecomment-762523614 https://api.github.com/repos/pydata/xarray/issues/4821 MDEyOklzc3VlQ29tbWVudDc2MjUyMzYxNA== keewis 14808389 2021-01-19T00:11:25Z 2021-01-19T00:12:04Z MEMBER

I think it's the way it is because tuple is hashable, so it can be used as a name: python ds = xr.Dataset({("a", 0): ("x", [1, 0])}) ds.sortby(("a", 0)) not sure if there's a particular use case where supporting this is crucial

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Error when supplying a tuple of dimensions to DataArray.sortby() 787847449

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