issue_comments
2 rows where issue = 122171841 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Is 'name' an xray supported attribute? · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 164632227 | https://github.com/pydata/xarray/issues/679#issuecomment-164632227 | https://api.github.com/repos/pydata/xarray/issues/679 | MDEyOklzc3VlQ29tbWVudDE2NDYzMjIyNw== | max-sixty 5635139 | 2015-12-15T03:16:34Z | 2015-12-15T03:16:34Z | MEMBER | Great, that's clear, cheers @shoyer |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Is 'name' an xray supported attribute? 122171841 | |
| 164617594 | https://github.com/pydata/xarray/issues/679#issuecomment-164617594 | https://api.github.com/repos/pydata/xarray/issues/679 | MDEyOklzc3VlQ29tbWVudDE2NDYxNzU5NA== | shoyer 1217238 | 2015-12-15T01:54:17Z | 2015-12-15T01:54:17Z | MEMBER |
Converting a list of DataArrays into a Dataset does sound like a useful thing, but to me that functionality is would be a closer fit for a hypothetical |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Is 'name' an xray supported attribute? 122171841 |
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