issue_comments

Table actions

1 row where issue = 987551524 and user = 14371165 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

  • Illviljan · 1 ✖

issue 1

  • Plotting of labelled data fails · 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
912625730 https://github.com/pydata/xarray/issues/5762#issuecomment-912625730 https://api.github.com/repos/pydata/xarray/issues/5762 IC_kwDOAMm_X842ZZBC Illviljan 14371165 2021-09-03T15:33:45Z 2021-09-03T15:55:05Z MEMBER

I think if you try out 0.19 you'll find that this works, see #5464. I just tried your example with <s>master</s> main and it works.

Though I'm not opposed to removing it, it makes sense to me to just trust the backend will do its job. But there's always some weird edge case that doesn't always make it that easy.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Plotting of labelled data fails 987551524

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