issue_comments

Table actions

1 row where issue = 584461380 and user = 4160723 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

  • benbovy · 1 ✖

issue 1

  • What should pad do about IndexVariables? · 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
1047947800 https://github.com/pydata/xarray/issues/3868#issuecomment-1047947800 https://api.github.com/repos/pydata/xarray/issues/3868 IC_kwDOAMm_X84-dmoY benbovy 4160723 2022-02-22T16:02:21Z 2022-02-22T16:02:21Z MEMBER

Would it be conceivable to implement an alternative form of coordinate index which is explicitly a linear coordinate axis, storing only a first point and a step (possibly a last point but that would obviously be redundant with the length of the dimension)

It would be possible to do that after the explicit index refactor is complete (see https://github.com/pydata/xarray/projects/1).

5692 already adds several Xarray methods like isel, sel, concat, stack, roll, rename, etc. to the new Xarray Index base class so that it will be possible to provide alternative indexes as Index sub-classes with custom implementations.

We could certainly add an Index.pad method.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   What should pad do about IndexVariables? 584461380

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