issue_comments

Table actions

1 row where issue = 621078539 and user = 2448579 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

  • dcherian · 1 ✖

issue 1

  • Unnamed dimensions · 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
1434959378 https://github.com/pydata/xarray/issues/4079#issuecomment-1434959378 https://api.github.com/repos/pydata/xarray/issues/4079 IC_kwDOAMm_X85Vh74S dcherian 2448579 2023-02-17T17:16:14Z 2023-02-17T17:16:22Z MEMBER

This reminds me of the issue with nan shaped dimensions. Where again we want to avoid automatic alignment (well in that case you can't align).

For this particular issue could we define a xr.UNNAMED that doesn't equal itself (hmm... would np.nan work?). Would that skip alignment checks?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Unnamed dimensions 621078539

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