issue_comments

Table actions

1 row where issue = 803075280 and user = 6628425 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: issue

user 1

  • spencerkclark · 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
808602928 https://github.com/pydata/xarray/issues/4880#issuecomment-808602928 https://api.github.com/repos/pydata/xarray/issues/4880 MDEyOklzc3VlQ29tbWVudDgwODYwMjkyOA== spencerkclark 6628425 2021-03-27T00:26:32Z 2021-03-27T00:26:32Z MEMBER

Yes I think unfortunately there is not much we can do here, since as @keewis noted, data_frame.coords["time"].data is a NumPy array.

This issue in general is a little tricky since xarray and pandas use nanosecond-precision datetime values, but datetime.datetime objects only have microsecond precision. See also discussion in https://github.com/numpy/numpy/issues/8546, https://github.com/numpy/numpy/issues/12550, and https://github.com/pydata/xarray/issues/3256.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Datetime as coordinaets does not convert back to datetime (returns int) 803075280

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