Did you try to run OPTIMIZE TABLE, REPAIR TABLE or ALTER TABLE on
those tables? If you run an ALTER TABLE table_name TYPE=old_type (be
sure to replace old_type with whatever the table currently is), it
should rebuild the table.
Check the docs on mysql.com, there are a bunch of pages about
upgrading between version. On possible probablem you could be facing
in change in how whitespace is handled in indexes.
On 12/30/05, Christian Meisinger <c.meisinger@stripped> wrote:
> Gary Richardson wrote:
> > We moved directly from 4.0.20 to 5.0.16. Worked like a charm. I had a
> > script that went through and optimized all tables with keys on
> > text/varchar and char fields.
> >
> > We're also slowly ALTERing innodb tables to get them into the new
> > compact format.
>
> i tryed to update from 4.1.15 to 5.0.17.
>
> it was a disaster...
>
> many varchar columns showed corrupted data after the update.
> can i do anything in mysql 4.1.15 to make the update work or is my
> only solution a complete dump and insert?
>
>
> best regards chris
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
>
>
