issue_comments

Table actions

1 row where author_association = "MEMBER" and issue = 254927382 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

issue 1

  • Multidimensional reindex · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
331481811 https://github.com/pydata/xarray/issues/1553#issuecomment-331481811 https://api.github.com/repos/pydata/xarray/issues/1553 MDEyOklzc3VlQ29tbWVudDMzMTQ4MTgxMQ== fujiisoup 6815844 2017-09-22T15:35:53Z 2017-09-22T15:35:53Z MEMBER

Suggestion about the coordinate dropping rule for reindex (ported from shoyer's comment)

  • For reindex(), indexing coordinates take precedence in the result ([kwargs[k] for k in kwargs] for obj.reindex(**kwargs)). Conflicts with indexed coordinates on the indexed object are silently ignored.

Which we would use with normal rule for dimension/non-dimension coordinates:

  • Conflicts between dimension coordinates (except for precedence) result in an error.
  • Conflicts between non-dimension coordinates result in silently dropping the conflicting variable.
 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Multidimensional reindex 254927382

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