issue_comments: 1033366312
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/402#issuecomment-1033366312 | https://api.github.com/repos/simonw/sqlite-utils/issues/402 | 1033366312 | IC_kwDOCGYnMM49l-so | 9599 | 2022-02-09T05:28:11Z | 2022-02-09T07:28:48Z | OWNER | My hunch is that the case where you want to consider input from more than one column will actually be pretty rare - the only case I can think of where I would want to do that is for latitude/longitude columns - everything else that I'd want to use it for (which admittedly is still mostly SpatiaLite stuff) works against a single value. The reason I'm leaning towards using the constructor for the values is that I really like the look of this variant for common conversions: ```python db["places"].insert( { "name": "London", "boundary": GeometryFromGeoJSON({...}) } ) ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 1125297737 |