issue_comments

Table actions

1 row where issue = 337202341 and user = 6815844 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1

  • fujiisoup · 1 ✖

issue 1

  • Plotting: do not check for monotonicity with 2D coords · 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
401607307 https://github.com/pydata/xarray/pull/2260#issuecomment-401607307 https://api.github.com/repos/pydata/xarray/issues/2260 MDEyOklzc3VlQ29tbWVudDQwMTYwNzMwNw== fujiisoup 6815844 2018-07-01T13:34:05Z 2018-07-01T13:34:05Z MEMBER

That's nice. Thanks:)

What will happen if the coordinate is a MultiIndex ? I often encounter this issue and am insisted to drop the coordinate manually. If it automatically drops the MultiIndex for plotting, that would be nicer.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Plotting: do not check for monotonicity with 2D coords 337202341

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