issue_comments: 507051067
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/23#issuecomment-507051067 | https://api.github.com/repos/simonw/sqlite-utils/issues/23 | 507051067 | MDEyOklzc3VlQ29tbWVudDUwNzA1MTA2Nw== | 9599 | 2019-06-30T16:54:08Z | 2019-06-30T16:59:05Z | OWNER | There could be a version of this which inserts the related record into the other table if it is missing, but reuses it if it's already there. That might look like this: db["events"].m2m(3, "venues", { "id": 4, "venue_name": "Blah", "latitude": 37.77 "longitude": 122.42 }, pk="id") Since this is doing an `.upsert()` against `venues`, the `.m2m()` method could accept all of the other arguments to `.upsert()` - probably `pk=`, `column_order=` and `ignore=True` as well (actually borrowed from `.insert(...)`, it would mean don't update this row if you find it). | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 449565204 |