issue_comments

Table actions

1 row where issue = 424538928 and user = 2539336 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

  • volkerjaenisch · 1 ✖

issue 1

  • Cannot store data after group_by · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
475964357 https://github.com/pydata/xarray/issues/2847#issuecomment-475964357 https://api.github.com/repos/pydata/xarray/issues/2847 MDEyOklzc3VlQ29tbWVudDQ3NTk2NDM1Nw== volkerjaenisch 2539336 2019-03-24T14:26:14Z 2019-03-24T14:26:14Z NONE

Thank you @spencerkclark for the fast response. I did exactly as you advices and it works fine. A hint in the documentation may hinder others to fall into this pit. Also it would be nice to have intervals serialized into netCDF since they are quite common structures.

Cheers, Volker

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Cannot store data after group_by 424538928

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