issue_comments

Table actions

1 row where issue = 820480606 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • shoyer · 1 ✖

issue 1

  • A read-only TileDB backend · 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
790140398 https://github.com/pydata/xarray/issues/4987#issuecomment-790140398 https://api.github.com/repos/pydata/xarray/issues/4987 MDEyOklzc3VlQ29tbWVudDc5MDE0MDM5OA== shoyer 1217238 2021-03-03T23:12:37Z 2021-03-03T23:12:37Z MEMBER

@jp-dark How would you feel about writing another small library, e.g., "xarray-tiledb" that can explicitly depend on both xarray and tiledb?

We can potentially do some of xarray's backend stuff with protocols, but there are some aspects (especially for more advanced features like lazy loading) that will likely need the hard xarray dependency.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A read-only TileDB backend 820480606

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