issue_comments

Table actions

1 row where issue = 830507003 and user = 88113 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

  • joshmoore · 1 ✖

issue 1

  • Saving zarr to remote location lower cases all data_vars · 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
860879523 https://github.com/pydata/xarray/issues/5028#issuecomment-860879523 https://api.github.com/repos/pydata/xarray/issues/5028 MDEyOklzc3VlQ29tbWVudDg2MDg3OTUyMw== joshmoore 88113 2021-06-14T17:58:36Z 2021-06-14T17:58:36Z NONE

A heads up that https://github.com/zarr-developers/zarr-python/pull/755 reverses the default behavior of FSStore and so as of Zarr 2.8.3 this might "just work"?

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Saving zarr to remote location lower cases all data_vars 830507003

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