issue_comments

Table actions

2 rows where issue = 587895591 and user = 14808389 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

  • keewis · 2 ✖

issue 1

  • Keep attrs by default? (keep_attrs) · 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
773693380 https://github.com/pydata/xarray/issues/3891#issuecomment-773693380 https://api.github.com/repos/pydata/xarray/issues/3891 MDEyOklzc3VlQ29tbWVudDc3MzY5MzM4MA== keewis 14808389 2021-02-05T00:25:16Z 2021-02-05T00:25:16Z MEMBER

if I remember correctly, we decided to allow passing a user-provided function to combine_attrs and to extend keep_attrs to accept a bool, a str or a function.

Something to keep in mind is that not all strategies make sense for operations that involve only a single variable, like isnull, but I guess for those all string options except drop mean "keep the attributes".

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Keep attrs by default? (keep_attrs) 587895591
766953351 https://github.com/pydata/xarray/issues/3891#issuecomment-766953351 https://api.github.com/repos/pydata/xarray/issues/3891 MDEyOklzc3VlQ29tbWVudDc2Njk1MzM1MQ== keewis 14808389 2021-01-25T16:51:00Z 2021-01-25T16:51:00Z MEMBER

I did not think this through carefully, but I wonder if we should extend merge_attrs to also take a function with a list of attrs as its only parameter and move towards something like combine_attrs instead of keep_attrs: setting keep_attrs seems to choose between combine_attrs="drop" and combine_attrs="override".

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Keep attrs by default? (keep_attrs) 587895591

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