issue_comments

Table actions

1 row where issue = 646130205 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

These facets timed out: author_association, issue

user 1

  • shoyer · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
650415181 https://github.com/pydata/xarray/issues/4185#issuecomment-650415181 https://api.github.com/repos/pydata/xarray/issues/4185 MDEyOklzc3VlQ29tbWVudDY1MDQxNTE4MQ== shoyer 1217238 2020-06-26T21:39:15Z 2020-06-26T21:39:15Z MEMBER

Could you give an example of the bad behavior for unstack()?

I am loathe to add global options because they tend to cause trouble for composability (e.e., you enable the option for your project and then it breaks the library you are using). But at least unstack() sounds like a real bug.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Keep single-value coordinates as dimensions 646130205

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