issue_comments: 507053558
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-507053558 | https://api.github.com/repos/simonw/sqlite-utils/issues/23 | 507053558 | MDEyOklzc3VlQ29tbWVudDUwNzA1MzU1OA== | 9599 | 2019-06-30T17:34:29Z | 2019-06-30T17:34:29Z | OWNER | Or... how about we use chaining like this: ```python db["events"].insert({...}, pk="id").m2m("venues", {...}, pk="id") ``` This makes me think that maybe there should be some kind of mechanism for saying "I'd should always be treated as a primary key". Maybe as an argument passed to the `Database` constructor. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 449565204 |