issue_comments

Table actions

1 row where issue = 773717776 and user = 35919497 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

  • aurghs · 1 ✖

issue 1

  • Fix warning on chunks compatibility · 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
750313634 https://github.com/pydata/xarray/pull/4726#issuecomment-750313634 https://api.github.com/repos/pydata/xarray/issues/4726 MDEyOklzc3VlQ29tbWVudDc1MDMxMzYzNA== aurghs 35919497 2020-12-23T14:02:54Z 2020-12-23T14:29:21Z COLLABORATOR

Btw & not for here. There are other warnings from the backends refactor. Would be nice if you could hunt them down and either fix or suppress them.

I was just doing that now. Some of them are fixed in https://github.com/pydata/xarray/pull/4728. 

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix warning on chunks compatibility 773717776

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