issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 187393785 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association

user 1

  • max-sixty · 2 ✖

issue 1

  • Transpose some but not all dimensions · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
544358202 https://github.com/pydata/xarray/issues/1081#issuecomment-544358202 https://api.github.com/repos/pydata/xarray/issues/1081 MDEyOklzc3VlQ29tbWVudDU0NDM1ODIwMg== max-sixty 5635139 2019-10-21T05:46:19Z 2019-10-21T05:46:19Z MEMBER

I would vote for (2), given it's fairly easy to replicate (1) by passing the full list, and I think (2) is arguably slightly more expected

(NB this isn't how #3421 works now, but easy to change)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Transpose some but not all dimensions 187393785
342898298 https://github.com/pydata/xarray/issues/1081#issuecomment-342898298 https://api.github.com/repos/pydata/xarray/issues/1081 MDEyOklzc3VlQ29tbWVudDM0Mjg5ODI5OA== max-sixty 5635139 2017-11-08T17:48:20Z 2017-11-08T17:48:20Z MEMBER

ds.transpose('lat', 'lon') seems pretty unambiguous.

Though I think that would have radically different behavior for a 2-dim or 3-dim case. For the 2-dim case, it would enforce that order regardless of original order. For the 3-dim case, are you proposing they're swapped from their current order?

(Maybe transpose naturally refers to the behavior I think you describe, we'd need something else to 'set this order')

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Transpose some but not all dimensions 187393785

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