issue_comments

Table actions

1 row where issue = 1078656323 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

issue 1

  • Broadcasting doesn't respect scalar coordinates · 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
992955585 https://github.com/pydata/xarray/issues/6075#issuecomment-992955585 https://api.github.com/repos/pydata/xarray/issues/6075 IC_kwDOAMm_X847L0zB max-sixty 5635139 2021-12-13T22:10:13Z 2021-12-13T22:10:13Z MEMBER

I can see why this is a bit surprising. I imagine the issue is that x is no longer a dimension; i.e.

``` x int64 2

vs

  • x (x) int64 1 2 3 ```

I think that's correct behavior, given the dimensions of the array have now changed. So I think the question is how we should combine non-dim coords with dim coords — possibly more strictly than we do now...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Broadcasting doesn't respect scalar coordinates 1078656323

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