issue_comments

Table actions

2 rows where author_association = "MEMBER" and issue = 124129804 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • Dataset.T property creates conflict with data named 'T' · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
167678835 https://github.com/pydata/xarray/issues/687#issuecomment-167678835 https://api.github.com/repos/pydata/xarray/issues/687 MDEyOklzc3VlQ29tbWVudDE2NzY3ODgzNQ== jhamman 2443309 2015-12-28T23:29:25Z 2015-12-28T23:29:25Z MEMBER

Agreed, I don't think we want to get rid of the transpose method T. A better solution for you would probably be to rename your temperature variable using the rename method. I often do this when comparing multiple datasets that use different variable naming conventions.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset.T property creates conflict with data named 'T' 124129804
167668470 https://github.com/pydata/xarray/issues/687#issuecomment-167668470 https://api.github.com/repos/pydata/xarray/issues/687 MDEyOklzc3VlQ29tbWVudDE2NzY2ODQ3MA== max-sixty 5635139 2015-12-28T22:17:42Z 2015-12-28T22:17:42Z MEMBER

Removing .T would break so much existing code, I don't think that's going to get much support. It's also consistent with numpy.

If you use IPython, tab-complete will work, so if your column is called temperature, you can access it almost as quickly...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset.T property creates conflict with data named 'T' 124129804

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