issue_comments

Table actions

1 row where issue = 702373263 and user = 22488770 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

  • andrewpauling · 1 ✖

issue 1

  • assign_coords with datetime64[us] changes dtype to datetime64[ns] · 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
696258727 https://github.com/pydata/xarray/issues/4427#issuecomment-696258727 https://api.github.com/repos/pydata/xarray/issues/4427 MDEyOklzc3VlQ29tbWVudDY5NjI1ODcyNw== andrewpauling 22488770 2020-09-21T17:28:34Z 2020-09-21T17:28:34Z CONTRIBUTOR

Thanks @spencerkclark for the response, that makes sense. I have been able to get what I needed to work using cftime, it just seemed strange to me that xarray behaved as it did with datetime64.

I agree it would be nice if an error was raised when dates can't be represented, would this be difficult to implement? I have been hoping to contribute to some open-source projects so if it's not too complex I'd be happy to tackle it, and if you have any advice on where to start with this problem that would be great.

 
{
    "total_count": 2,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 2,
    "rocket": 0,
    "eyes": 0
}
   assign_coords with datetime64[us] changes dtype to datetime64[ns] 702373263

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