issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 115897556 and user = 1217238 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

  • shoyer · 1 ✖

issue 1

  • error when using broadcast_arrays with coordinates · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
155284553 https://github.com/pydata/xarray/issues/649#issuecomment-155284553 https://api.github.com/repos/pydata/xarray/issues/649 MDEyOklzc3VlQ29tbWVudDE1NTI4NDU1Mw== shoyer 1217238 2015-11-10T04:33:14Z 2015-11-10T04:33:14Z MEMBER

This is yet another issue that magically just works after merging #648!

I'll add your example to the test suite as a regression test.

I was actually holding off on widely advertising xray.broadcast_arrays for exactly this reason -- there wasn't an easy way to fix this before, and this was a pretty obvious edge case. Now I think we can probably safely guarantee the behavior of broadcast_arrays.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   error when using broadcast_arrays with coordinates 115897556

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