issue_comments: 553171011
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/simonw/sqlite-utils/issues/66#issuecomment-553171011 | https://api.github.com/repos/simonw/sqlite-utils/issues/66 | 553171011 | MDEyOklzc3VlQ29tbWVudDU1MzE3MTAxMQ== | 9599 | 2019-11-12T23:50:52Z | 2019-11-12T23:50:52Z | OWNER | Fixing this is going to be a real pain. There's lots of code out there that uses `sqlite-utils` with the expectation that `upsert()` behaves as it currently does. Maybe I need to introduce new terms for both of these different patterns and deprecate the existing `.upsert()` and `.upsert_all()` since their behaviour can't be changed? Or maybe I fix this and ship `sqlite-utils 2.0` with a breaking change? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 521868864 |