Hallo!
To Gleb Paharenko:
Thank you for your answer!
When I am upgrading from MySql 4.0 to 5.0 it is recommanded to dump in
4.0 and restore in 5.0. Therefore I can not use mysqldump of 5.0,
because if I can simply open the databases with 5.0 I do not have to
dump and restore. And of course
Hallo!
Thank all of you for your answers!
As my answers are not posted to my questions, I copy the whole text
here. I am not subscribed to the mailing list and therefore not reply
but send my answers with same subject. This worked the last time I
answered to a mail. Perhaps someone can tell
So no answer is an answer too!
As nobody wants to answer me, I have to suppose that INSERTS are slower now,
but no one dares to confess it. It is not my intention to talk bad about MySql,
I only want to know the truth and the reason for it and perhaps a hope that it
will get faster again in f
So no answer is an answer too!
As nobody wants to answer me, I have to suppose that INSERTS are slower
now, but no one dares to confess it. It is not my intention to talk bad
about MySql, I only want to know the truth and the reason for it and
perhaps a hope that it will get faster again in fu
Hello!
I wanted to upgrade from 4.0.16 to 5.0.16, but already notized a slow
performance on restoring data with INSERTS.
When dumping a table with mysqldump (4.0.16) and then restoring it with
mysql <<, which consists only of
INSERTS, the duration increases.
For test reasons I have tried it
