issue_comments

Table actions

where issue = 30656827 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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
39388919 https://github.com/pydata/xarray/pull/88#issuecomment-39388919 https://api.github.com/repos/pydata/xarray/issues/88 MDEyOklzc3VlQ29tbWVudDM5Mzg4OTE5 shoyer 1217238 2014-04-02T21:54:14Z 2014-04-02T21:54:14Z MEMBER

The bigger problem with redundant coordinates would be other machinery (e.g., for broadcasting arrays) which assumes that coordinates are unique.

For this function, the second use of the coordinate just wouldn't appear in the representation. My guess is that most functions should degrade relatively gracefully (like this one), because I usually use array.dimensions.index(dim) to determine axis numbers, which returns the first index in which dim appears.

If we want to support arrays with duplicate dimensions, we should definitely add some test cases.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: Better Dataset repr 30656827

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