issue_comments: 886122696

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-886122696 https://api.github.com/repos/simonw/sqlite-utils/issues/251 886122696 IC_kwDOCGYnMM400SjI 9599 2021-07-24T23:21:32Z 2021-07-24T23:21:32Z OWNER

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()'

This is a bit verbose - and having added --multi and --output the lambda command keeps getting more and more flexible compared to the others.

New idea: ditch the sub-sub-commands and move the jsonsplit and parsedate recipes to be options of convert - maybe like this:

sqlite-utils convert my.db mytable col1 --jsonsplit

or:

sqlite-utils convert my.db mytable col1 --recipe jsonsplit

or -r jsonsplit for short.

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