issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 1477931237 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

These facets timed out: author_association, issue

user 1

  • dcherian · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1346767759 https://github.com/pydata/xarray/pull/7361#issuecomment-1346767759 https://api.github.com/repos/pydata/xarray/issues/7361 IC_kwDOAMm_X85QRguP dcherian 2448579 2022-12-12T15:51:55Z 2022-12-12T15:52:31Z MEMBER

I don't know how many people use the lower level methods of CFTimeIndexes like get_loc outside of xarray data structures.

I sometimes do this with a general pd.Index but it's pretty rare. In any case, I think any user using get_loc would be fairly advanced and can figure out the workaround pretty easily.

@aulemahal does xclim or its related packages use CFTimeIndex.get_loc at all to convert a label to an integer index?(EDIT: a search didn't turn up anything)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   COMPAT: Adjust CFTimeIndex.get_loc for pandas 2.0 deprecation enforcement 1477931237

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