issue_comments

Table actions

2 rows where issue = 484089737 and user = 5635139 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

  • max-sixty · 2 ✖

issue 1

  • assign_coords adds coordinates without a new dimension if the value is scalar · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
524527361 https://github.com/pydata/xarray/issues/3240#issuecomment-524527361 https://api.github.com/repos/pydata/xarray/issues/3240 MDEyOklzc3VlQ29tbWVudDUyNDUyNzM2MQ== max-sixty 5635139 2019-08-24T07:09:04Z 2019-08-24T07:09:04Z MEMBER

In that example, y has no dimensions that aren't on the array. So while it is a bit unusual, the resulting object doesn't break any rules / invariants. Does that make sense?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   assign_coords adds coordinates without a new dimension if the value is scalar 484089737
524025546 https://github.com/pydata/xarray/issues/3240#issuecomment-524025546 https://api.github.com/repos/pydata/xarray/issues/3240 MDEyOklzc3VlQ29tbWVudDUyNDAyNTU0Ng== max-sixty 5635139 2019-08-22T18:35:02Z 2019-08-22T18:35:02Z MEMBER

Interesting case, thanks for posting.

There's some logic that this could be allowed - it's a coord along no dimensions (whereas in the previous case it had to be on a dimension, unspecified).

But that's what attributes are, so I'm not sure whether this is something we should support.

Does anyone know whether this is a deliberate decision?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   assign_coords adds coordinates without a new dimension if the value is scalar 484089737

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