issue_comments: 890446506

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/251#issuecomment-890446506 https://api.github.com/repos/simonw/sqlite-utils/issues/251 890446506 IC_kwDOCGYnMM41EyKq 9599 2021-08-01T04:16:36Z 2021-08-01T04:16:36Z OWNER

Back to the design board then. One way to handle this would be the long-form:

sqlite-utils convert jsonsplit mydb.db mytable mycolumn sqlite-utils convert parsedatetime mydb.db mytable mycolumn sqlite-utils convert parsedate mydb.db mytable mycolumn sqlite-utils convert lambda mydb.db mytable mycolumn --code='str(value).upper()' I like the idea that lambda is the default action, but in this form it's required that the second argument (the word after convert) be the name of the recipe that is being applied to avoid any potential confusion with the database filename.

An ugly solution would be to make all four of those options available on sqlite-utils convert - and return an error if you try and use one of those without specifying the accompanying recipe. That's a bit gross though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 841377702