issue_comments

Table actions

3 rows where author_association = "CONTRIBUTOR", issue = 690546795 and user = 90008 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

  • hmaarrfk · 3 ✖

issue 1

  • [WIP] Support nano second time encoding. · 3 ✖

author_association 1

  • CONTRIBUTOR · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1484222279 https://github.com/pydata/xarray/pull/4400#issuecomment-1484222279 https://api.github.com/repos/pydata/xarray/issues/4400 IC_kwDOAMm_X85Yd29H hmaarrfk 90008 2023-03-26T20:59:00Z 2023-03-26T20:59:00Z CONTRIBUTOR

nice!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [WIP] Support nano second time encoding. 690546795
735759416 https://github.com/pydata/xarray/pull/4400#issuecomment-735759416 https://api.github.com/repos/pydata/xarray/issues/4400 MDEyOklzc3VlQ29tbWVudDczNTc1OTQxNg== hmaarrfk 90008 2020-11-30T12:33:33Z 2020-11-30T12:33:33Z CONTRIBUTOR

I think you should be able to define your own custom encoder if you want it to be a datetime.

But inevitably, you will have to define your own save and load functions.

Python, by definition of being such a loose language, allows you to do things that the original developers never really imagined.

this can sometimes lead to silent corruption.like the one you've experienced.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [WIP] Support nano second time encoding. 690546795
735428578 https://github.com/pydata/xarray/pull/4400#issuecomment-735428578 https://api.github.com/repos/pydata/xarray/issues/4400 MDEyOklzc3VlQ29tbWVudDczNTQyODU3OA== hmaarrfk 90008 2020-11-29T17:32:37Z 2020-11-29T17:32:37Z CONTRIBUTOR

yeah, i'm not too sure. I think the idea is that this breaks compatibility with netcdf times, so the resulting file is thus not standard.

For my application, us timing is enough.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [WIP] Support nano second time encoding. 690546795

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