issue_comments
2 rows where issue = 565626748 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- `where` ignores incorrectly typed arguments · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 587149607 | https://github.com/pydata/xarray/issues/3770#issuecomment-587149607 | https://api.github.com/repos/pydata/xarray/issues/3770 | MDEyOklzc3VlQ29tbWVudDU4NzE0OTYwNw== | shoyer 1217238 | 2020-02-17T20:36:37Z | 2020-02-17T20:36:37Z | MEMBER | I'd be OK with callable support in where() and other methods, as long as we have a clear policy about what methods should/will support it. On Mon, Feb 17, 2020 at 11:29 AM keewis notifications@github.com wrote:
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
`where` ignores incorrectly typed arguments 565626748 | |
| 586653324 | https://github.com/pydata/xarray/issues/3770#issuecomment-586653324 | https://api.github.com/repos/pydata/xarray/issues/3770 | MDEyOklzc3VlQ29tbWVudDU4NjY1MzMyNA== | shoyer 1217238 | 2020-02-16T00:01:54Z | 2020-02-16T00:01:54Z | MEMBER | This is a NumPy thing, too:
(I don't really understand why that is the case, but it does seem to be well-established behavior in Python) |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
`where` ignores incorrectly typed arguments 565626748 |
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 1