issue_comments

Table actions

1 row where author_association = "NONE" and issue = 982973379 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

issue 1

  • datetime64 data type in arrays is always 'datetime64[ns]' · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
908526277 https://github.com/pydata/xarray/issues/5750#issuecomment-908526277 https://api.github.com/repos/pydata/xarray/issues/5750 IC_kwDOAMm_X842JwLF sjsmith757 45645265 2021-08-30T17:15:49Z 2021-08-30T17:15:49Z NONE

Actually I am guessing this is related to the underlying pandas.DatetimeIndex, which I guess only supports units of 'ns'. So perhaps there isn't much that can be done at this time, but it is not ideal to have to go to pandas documentation to see that. It is sort of suggested here, but perhaps it could be made more explicit

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   datetime64 data type in arrays is always 'datetime64[ns]' 982973379

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