issue_comments
2 rows where issue = 911663002 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Add Union Operators for Dataset · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 854862270 | https://github.com/pydata/xarray/issues/5438#issuecomment-854862270 | https://api.github.com/repos/pydata/xarray/issues/5438 | MDEyOklzc3VlQ29tbWVudDg1NDg2MjI3MA== | TomNicholas 35968931 | 2021-06-04T16:35:36Z | 2021-06-04T16:35:36Z | MEMBER | Oh, I didn't realise that! Forget about this idea then :disappointed: |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Add Union Operators for Dataset 911663002 | |
| 854861307 | https://github.com/pydata/xarray/issues/5438#issuecomment-854861307 | https://api.github.com/repos/pydata/xarray/issues/5438 | MDEyOklzc3VlQ29tbWVudDg1NDg2MTMwNw== | shoyer 1217238 | 2021-06-04T16:33:54Z | 2021-06-04T16:33:54Z | MEMBER | My main concern here is that these binary operators already have a meaning on Union operators would be convenient, but writing out |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Add Union Operators for Dataset 911663002 |
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 2