issue_comments

Table actions

1 row where issue = 1361989642 and user = 4160723 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

  • benbovy · 1 ✖

issue 1

  • New MultiIndex dimension behaviours · 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
1237981036 https://github.com/pydata/xarray/issues/6990#issuecomment-1237981036 https://api.github.com/repos/pydata/xarray/issues/6990 IC_kwDOAMm_X85Jyhds benbovy 4160723 2022-09-06T10:44:08Z 2022-09-06T10:44:08Z MEMBER

Hi @ConnorSwales,

Yes this is an intentional change part of the ongoing explicit indexes refactor. There's still some work to do on the documentation. For more details, see:

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   New MultiIndex dimension behaviours 1361989642

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