issue_comments

Table actions

1 row where author_association = "NONE", issue = 514077742 and user = 7123715 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

  • cvoivret · 1 ✖

issue 1

  • Keep index dimension when selecting only a single coord · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
788661534 https://github.com/pydata/xarray/issues/3458#issuecomment-788661534 https://api.github.com/repos/pydata/xarray/issues/3458 MDEyOklzc3VlQ29tbWVudDc4ODY2MTUzNA== cvoivret 7123715 2021-03-02T06:48:08Z 2021-03-02T06:48:08Z NONE

Hi, I'm new to OSS and I would like to take this issue. After some digging, the initial question seems to be related to vectorized indexing. We could add in a code block multiple ways to extract a column (and keep the second dimension) in the beginning of the section. It is rather specific example but, as @dcherian say, it comes up oftten enough. I can make it if the issue still matter.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Keep index dimension when selecting only a single coord 514077742

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