issue_comments

Table actions

1 row where issue = 1339129609 and user = 1197350 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

  • rabernat · 1 ✖

issue 1

  • Given zarr-backed Xarray determine store and group · 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
1216491512 https://github.com/pydata/xarray/issues/6916#issuecomment-1216491512 https://api.github.com/repos/pydata/xarray/issues/6916 IC_kwDOAMm_X85Igi_4 rabernat 1197350 2022-08-16T11:11:38Z 2022-08-16T11:11:38Z MEMBER

As a general principle, I think we should try to put enough information in encoding to enable one to re-open the dataset from scratch with the same parameters. So that would mean including the engine and other open_dataset options in encoding.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Given zarr-backed Xarray determine store and group 1339129609

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