in reply to Re^4: Encoding issue after upgrade
in thread Encoding issue after upgrade
It probably needs to be manually cleaned up as there is more data added since the move...
I would hazard a guess, that while the copy operation messed up the data, it messed it up in a very specific, methodical way. Probably all the bits of the data are still there (just in the wrong order/encoding) so with a bit of tinkering and math, you could possibly write a script to reverse the damage.
If you also have a copy of the old database, you could write a script that specifically updates the lines in the new database with the data from the old one, which would be even easier.
PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP
|
|---|
In Section
Seekers of Perl Wisdom