issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 211888882 and user = 10050469 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • fmaussion · 2 ✖

issue 1

  • Terminology for the various coordinates · 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
284345624 https://github.com/pydata/xarray/issues/1295#issuecomment-284345624 https://api.github.com/repos/pydata/xarray/issues/1295 MDEyOklzc3VlQ29tbWVudDI4NDM0NTYyNA== fmaussion 10050469 2017-03-06T09:32:19Z 2017-03-06T09:32:19Z MEMBER

I'm fine with this too. In particular, I find "dimension coordinate" much more meaningful than just "coordinate variable".

Do I read this correctly that we agree on: - dimension coordinates - non-dimension coordinates ?

I'm also fine with "auxiliary coordinates" for the second type. Let me know which one we should pick, I'll update the PR accordingly.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Terminology for the various coordinates 211888882
284213319 https://github.com/pydata/xarray/issues/1295#issuecomment-284213319 https://api.github.com/repos/pydata/xarray/issues/1295 MDEyOklzc3VlQ29tbWVudDI4NDIxMzMxOQ== fmaussion 10050469 2017-03-05T08:23:20Z 2017-03-05T08:23:20Z MEMBER

Thanks @rabernat , I think this makes sense. I like "dimension coordinate" better and less ambiguous than "coordinate variable", but staying in line with CF clearly is the best thing to do here.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Terminology for the various coordinates 211888882

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