Upgrading 4.1.1alpha to 4.1.20 - VARCHAR fields data truncated
Hi All, thanks in advance for reading this.
I think I got a complicated situation here.
I have Mysql 4.1.1alpha runing on an old Fedora 1 box, and I am now upgrading to Mysql 4.1.20 on CentOS.
Ive made dumps with mysqldump on 4.1.1alpha, and restored them on my new box with version 4.1.20. Everything seems ok, since I discovered that fields of type VARCHAR, was receiving data truncated. Like, on version 4.1.1alpha, Mysql was accepting the insertion of fields longer than the initial definition of VARCHAR(60). The data in the dump file is OK (fields longer than 60).
The problem is that all data got truncated on my new box after the restore procedure (mysql < dump_file.sql), on Mysql 4.1.20.
I was searching realese notes for version 4.1.2 or other, so I can find it was a bug or so, but I coulnt find any notes.
Well, my problem is obvios: I need to make the new version (4.1.20) behave like 4.1.1alpha and accept those fields ignoring size definitions, so I dont have to rebuild my whole application, and search lots of tables, adjusting sizes and stuff. Of course, Im trying the most easy and low cost option.
(I also did a hard copy of my database files from /var/lib/mysql, to the new machine with version 4.1.20, and it worked. The databases are ok now. But I end up with the same problem when I consider future inserts or UPDATES on theses tables will truncate the fields that are already stored on these tables)
The big question is: Is there an option to make Mysql ignore those fields size limits and bahave just like version 4.1.1alpha?
Thanks again,
Gustavo