issue_comments

Table actions

1 row where issue = 575564170 and user = 7441788 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

  • seth-p · 1 ✖

issue 1

  • {DataArray,Dataset} accessors with parameters · 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
594682466 https://github.com/pydata/xarray/issues/3829#issuecomment-594682466 https://api.github.com/repos/pydata/xarray/issues/3829 MDEyOklzc3VlQ29tbWVudDU5NDY4MjQ2Ng== seth-p 7441788 2020-03-04T17:27:09Z 2020-03-04T17:27:09Z CONTRIBUTOR

@keewis, thanks for the suggestions. Both seem reasonable.

In your first example, if you wanted to prohibit obj.weighted.sum(dim), you could just check for self._weight in sum(). Though I suppose it would be nice to be able to have the interpreter enforce the requirement and not have to do an explicit check in every method.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   {DataArray,Dataset} accessors with parameters 575564170

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