Christian Hammers wrote:
Hello Alexis
Hi Christian
Maybe your innodb data files were corrupted somewhen else and the problem only just appeared at this occasion. If you try to reproduce it in a second database on your host, e.g. in a chroot so it uses a different inndb table space file, do you get the same error?
I'm going to try that, but FYI, after having downgraded mysql-server to the sarge version (4.x) the bug disappeared (using the same dump files).
Until we proved that this is a general problem I downgraded the bugreport as it would prevent 5.0.32 from entering testing/etch. But please try to reproduce it again on your computer, maybe I just did something different.
I understand, I'm going to try reproduce it in a chroot with etch's mysql-server.
By the way, I'm wondering if that would be a good idea to provide both version 4 and 5 within etch instead of making the version 5 "provide" the 4. Don't you think?
Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
