issue_comments

Table actions

1 row where issue = 253349435 and user = 1197350 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

  • rabernat · 1 ✖

issue 1

  • Avoid computing dask variables on __repr__ and __getattr__ · 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
326632469 https://github.com/pydata/xarray/pull/1532#issuecomment-326632469 https://api.github.com/repos/pydata/xarray/issues/1532 MDEyOklzc3VlQ29tbWVudDMyNjYzMjQ2OQ== rabernat 1197350 2017-09-01T16:59:14Z 2017-09-01T16:59:14Z MEMBER

Just wanted to say that I'm so glad someone took this on!

Will this also fix the very slow tab-autocomplete on dask-backed xarray objects? This is something I hit frequently in interactive work with big datasets. I assume it's related.

 
{
    "total_count": 3,
    "+1": 3,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Avoid computing dask variables on __repr__ and __getattr__ 253349435

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