issue_comments
6 rows where issue = 132774456 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Ordered Groupby Keys · 6 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 556078259 | https://github.com/pydata/xarray/issues/757#issuecomment-556078259 | https://api.github.com/repos/pydata/xarray/issues/757 | MDEyOklzc3VlQ29tbWVudDU1NjA3ODI1OQ== | dcherian 2448579 | 2019-11-20T16:12:40Z | 2019-11-20T16:12:40Z | MEMBER | I use |
{
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Ordered Groupby Keys 132774456 | |
| 556062845 | https://github.com/pydata/xarray/issues/757#issuecomment-556062845 | https://api.github.com/repos/pydata/xarray/issues/757 | MDEyOklzc3VlQ29tbWVudDU1NjA2Mjg0NQ== | jbusecke 14314623 | 2019-11-20T15:45:33Z | 2019-11-20T15:45:33Z | CONTRIBUTOR | Just stumbled across this issue. Is there a recommended workaround? I am usually doing this (specific to seasons):
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Ordered Groupby Keys 132774456 | |
| 370123586 | https://github.com/pydata/xarray/issues/757#issuecomment-370123586 | https://api.github.com/repos/pydata/xarray/issues/757 | MDEyOklzc3VlQ29tbWVudDM3MDEyMzU4Ng== | tdihp 1396390 | 2018-03-03T06:27:13Z | 2018-03-03T06:27:13Z | NONE | Ahh, so it's sorted, instead of keeping the original order. I was expecting |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Ordered Groupby Keys 132774456 | |
| 182676967 | https://github.com/pydata/xarray/issues/757#issuecomment-182676967 | https://api.github.com/repos/pydata/xarray/issues/757 | MDEyOklzc3VlQ29tbWVudDE4MjY3Njk2Nw== | shoyer 1217238 | 2016-02-11T02:32:59Z | 2016-02-12T00:15:48Z | MEMBER | For what it's worth, I don't think we have any good solutions short of adding our own array type do to Categorical in xarray. We could set sort=False in some cases when we call pd.factorize but that's not a great alternative. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Ordered Groupby Keys 132774456 | |
| 182671718 | https://github.com/pydata/xarray/issues/757#issuecomment-182671718 | https://api.github.com/repos/pydata/xarray/issues/757 | MDEyOklzc3VlQ29tbWVudDE4MjY3MTcxOA== | jhamman 2443309 | 2016-02-11T02:01:05Z | 2016-02-11T02:01:05Z | MEMBER | Hmmm, a mystery. I'll look into this a bit more. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Ordered Groupby Keys 132774456 | |
| 182659762 | https://github.com/pydata/xarray/issues/757#issuecomment-182659762 | https://api.github.com/repos/pydata/xarray/issues/757 | MDEyOklzc3VlQ29tbWVudDE4MjY1OTc2Mg== | shoyer 1217238 | 2016-02-11T00:48:18Z | 2016-02-11T00:48:18Z | MEMBER | I agree this is annoying, but I don't think your diagnosis is correct here. The |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Ordered Groupby Keys 132774456 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 5