issue_comments

Table actions

1 row where issue = 124176573 and user = 5635139 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

  • max-sixty · 1 ✖

issue 1

  • Should Dataset enforce some ordering of dims in its variables? · 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
167879315 https://github.com/pydata/xarray/issues/689#issuecomment-167879315 https://api.github.com/repos/pydata/xarray/issues/689 MDEyOklzc3VlQ29tbWVudDE2Nzg3OTMxNQ== max-sixty 5635139 2015-12-29T21:20:56Z 2015-12-29T21:20:56Z MEMBER

Great, I didn't know transpose could do that, cheers. FWIW this doesn't seem to enforce the ordering of the dims of coords in a DataArray - let me know if you want me to open an issue / post an example.

I think that makes sense re enforcing the ordering. I think my current use case is very specific (applying functions to pandas objects, which don't recognize dims, and so fail if things are in the wrong order). More generally, I'd hope functions would be robust to the order of dimensions.

I'll close for now.

Thanks as ever!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Should Dataset enforce some ordering of dims in its variables? 124176573

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