issue_comments

Table actions

1 row where issue = 1130073503 and user = 1562854 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

  • jklymak · 1 ✖

issue 1

  • Date in matplotlib conversion does not handle "YYYY-MM-DD" format for xarray=0.21.1 · 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
1049066201 https://github.com/pydata/xarray/issues/6263#issuecomment-1049066201 https://api.github.com/repos/pydata/xarray/issues/6263 IC_kwDOAMm_X84-h3rZ jklymak 1562854 2022-02-23T18:09:32Z 2022-02-23T18:09:32Z CONTRIBUTOR

It could, after the units are set to dates, but all it would do is pass to datetime64, so the recommendation would be that users do that explicitly.

If the units are not set to dates (ie. this is the first call on the axis) then strings are interpreted as categories in Matplotlib, and all sorts of hilarity ensues if the strings are all dates....

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Date in matplotlib conversion does not handle "YYYY-MM-DD" format for xarray=0.21.1 1130073503

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