issue_comments

Table actions

1 row where issue = 789106802 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)

user 1

  • dcherian · 1 ✖

issue 1

  • clean up the API for renaming and changing dimensions / coordinates · 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
766914263 https://github.com/pydata/xarray/issues/4825#issuecomment-766914263 https://api.github.com/repos/pydata/xarray/issues/4825 MDEyOklzc3VlQ29tbWVudDc2NjkxNDI2Mw== dcherian 2448579 2021-01-25T15:54:14Z 2021-01-25T15:54:14Z MEMBER

I'm not sure exactly how to rationalize them though.

How about

  1. rename_* should only allow renaming to unused names,
  2. swap_dims should only work with existing names.
  3. set_index should raise an error for the "renaming" and "swapping" cases.
 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   clean up the API for renaming and changing dimensions / coordinates 789106802

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