No, I don't.
Probably ...
You can add a column "hashed_password" as a shadow to the right table, and hash all "plain_password" and gradually double all password write and reads in the code.
At the end delete or rename the plain_password field and "deactivate" all code referencing it. ¹
But that's something you gods must discuss!
Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery
¹) I'd probably encapsulate all this in two custom functions "store_password" and "check_password" which are ruled by a global switch.
In reply to Re^16: Ideas for "fixing" PerlMonks 1.0
by LanX
in thread Ideas for "fixing" PerlMonks 1.0
by etj
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |