issue_comments

Table actions

1 row where issue = 152478345 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • shoyer · 1 ✖

issue 1

  • Unintuitive broadcasting behavior · 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
216122656 https://github.com/pydata/xarray/issues/840#issuecomment-216122656 https://api.github.com/repos/pydata/xarray/issues/840 MDEyOklzc3VlQ29tbWVudDIxNjEyMjY1Ng== shoyer 1217238 2016-05-02T07:26:54Z 2016-05-02T07:26:54Z MEMBER

In the second multiplication, you are multiplying an array with dimensions (b,) by one with dimensions (a,b). This results in something with dimensions (b,a), because we broadcast dimensions in order of appearance.

I agree that it would be nice to swap dimensions back in assignment, at least in this context. But I'll just note that we currently don't do any alignment of RHS arguments in assignment operations, so we would need to think about the full implications of doing such alignment.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Unintuitive broadcasting behavior 152478345

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