issue_comments

Table actions

1 row where issue = 168754274 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)

user 1

  • shoyer · 1 ✖

issue 1

  • Dataset creation requires tuple, list treated differently · 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
236736739 https://github.com/pydata/xarray/issues/929#issuecomment-236736739 https://api.github.com/repos/pydata/xarray/issues/929 MDEyOklzc3VlQ29tbWVudDIzNjczNjczOQ== shoyer 1217238 2016-08-01T23:15:28Z 2016-08-01T23:15:28Z MEMBER

This difference is certainly intentional. You're right that we currently don't explicitly state how we handle lists or numpy arrays in the docs -- that should be fixed.

At one point, we did have heuristics that did this sort of fallback logic (allowing lists, and checking the length of the tuple/list). But we eventually removed these checks, because this sort of value dependent behavior makes code difficult to predict. At least now it always behaves consistently when given a list or a tuple.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset creation requires tuple, list treated differently 168754274

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