issue_comments

Table actions

1 row where issue = 1424215477 and user = 35968931 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • TomNicholas · 1 ✖

issue 1

  • Typing with Variadic Generics in python 3.11 (PEP 646) · 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
1292252691 https://github.com/pydata/xarray/issues/7227#issuecomment-1292252691 https://api.github.com/repos/pydata/xarray/issues/7227 IC_kwDOAMm_X85NBjYT TomNicholas 35968931 2022-10-26T15:48:36Z 2022-10-26T15:53:14Z MEMBER

Well that's frustrating - I didn't see that.

They also mention that if PEP 637 hadn't been rejected there would be more use, which is ironic because we also wanted PEP 637 for indexing (like da[time=slice(5, 10)]).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Typing with Variadic Generics in python 3.11 (PEP 646) 1424215477

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