issue_comments

Table actions

2 rows where issue = 933551030 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

issue 1

  • Flexible indexes: how best to implement the new data model? · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
877736473 https://github.com/pydata/xarray/issues/5553#issuecomment-877736473 https://api.github.com/repos/pydata/xarray/issues/5553 MDEyOklzc3VlQ29tbWVudDg3NzczNjQ3Mw== shoyer 1217238 2021-07-11T03:47:12Z 2021-07-11T03:47:12Z MEMBER

At the very least, I do think we need something like option 3. We don't want to be in a scenario where indexes can easily get out of sync.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Flexible indexes: how best to implement the new data model? 933551030
877736416 https://github.com/pydata/xarray/issues/5553#issuecomment-877736416 https://api.github.com/repos/pydata/xarray/issues/5553 MDEyOklzc3VlQ29tbWVudDg3NzczNjQxNg== shoyer 1217238 2021-07-11T03:46:04Z 2021-07-11T03:46:04Z MEMBER

Would we need to duplicate data with option 1? It seems like a wrapper that makes the data in a Variable immutable might resolve that? We could even compute the variable's data on the fly using Xarray's lazy indexing machinery.

I was initially leaning towards 2 due to cleaner handling of "virtual" coordinates, but I'm not so sure that that would actually help anymore.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Flexible indexes: how best to implement the new data model? 933551030

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