On So, Jun 5 2022 at 01:21:37 +0200, Sasi Olin <hellcp@opensuse.org> wrote:
What I'm thinking of doing would be to do two database imports, with different encodings set, one for data with the modify date before the breakage with the old encoding and then the other for data with the modify date after the breakage with the new encoding. The only real issue is finding the exact moment the database broke, which will be easier having the post above.
Update on this: picked the date based on that post, and it seems to work to an extent: all the posts after that date seem to be broken (because the db still uses latin1 encoding while vb keeps pushing utf8 content into it) Using ``` mysqldump --host=192.168.47.4 --port=3307 --user=vbulletin \ --password=$password --where "dateline > '1304923020'" webforums vb_post ``` I was able to see the breakage quite easily, and I am able to force mysql to export this as if it was a utf-8 database, so that we get both both parts of the database to be the correct encoding inside the dump Could we maybe create a copy of vb server (and its database), so that we could test what changes we actually need to make for this to work? And on that note, does anyone have a good idea how to find broken characters inside of the dump, so that we can find the earliest date with breakage (in other tables too, I was just using vb_post as an example, because it's the most obvious of the broken tables)? It shouldn't be too difficult to do in an automated way I would assume, but my process for this feels more manual than it probably should be. LCP [Sasi] https://lcp.world/