issue_comments: 1291152433
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/495#issuecomment-1291152433 | https://api.github.com/repos/simonw/sqlite-utils/issues/495 | 1291152433 | IC_kwDOCGYnMM5M9Wwx | 9599 | 2022-10-25T21:14:54Z | 2022-10-25T21:14:54Z | OWNER | There is a case where the function can return a dictionary at the moment: `multi=True` ```python table.convert( "title", lambda v: {"upper": v.upper(), "lower": v.lower()}, multi=True ) ``` But I think this change is still compatible with that. if you don't use `multi=True` then the return value will be stringified. If you DO use `multi=True` then something like this could work: ```python table.convert( "title", lambda v: {"upper": {"str": v.upper()}, "lower": {"str": v.lower()}}, multi=True ) ``` This would result in a `upper` and `lower` column, each containing the JSON string `{"str": "UPPERCASE"}`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 1392690202 |