issue_comments

Table actions

1 row where issue = 700915153 and user = 35968931 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

  • TomNicholas · 1 ✖

issue 1

  • circular + linear stats on a same dataset · 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
720090925 https://github.com/pydata/xarray/issues/4421#issuecomment-720090925 https://api.github.com/repos/pydata/xarray/issues/4421 MDEyOklzc3VlQ29tbWVudDcyMDA5MDkyNQ== TomNicholas 35968931 2020-11-01T13:44:25Z 2020-11-01T13:44:25Z MEMBER

To be able to treat periodic variables differently we would need the index for a dimension underlying the variable to know that the variable is periodic in that direction. That should hopefully be one of the features that will become possible after the Explicit Indexes Refactor. Until then I can't think of any other tricks to make this work.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   circular + linear stats on a same dataset 700915153

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