Re: Error 1406

[Gleb Paharenko]

Hello.

>I also tried modifying the mediumtext to longtext in the dumpfile but it produces a
> column
>with a -1 size for some reason.

Please, could you provide a snip from your dump file.

>When I try to input it back into the new 5.0 database, it gives me this error (1406
> data
>too long for column)

Check your sql_mode system variable, if you have there STRICT_ALL_TABLES
or STRICT_TRANS_TABLES values. Due to this all warnings are converted to
errors and import fails. In 4.0 you might have the same problems, but
server just doesn't produce warnings, and you don't know what's going
on.



"James Sherwood" <jsherwood@stripped> wrote:
>ello,
>
>I dumped a database from our 4.0 server to a .sql file.
>
>When I try to input it back into the new 5.0 database, it gives me this error (1406
> data
>too long for column)
>
>This works fine on 4.0 but will not work on 5.0.
>
>I also tried modifying the mediumtext to longtext in the dumpfile but it produces a
> column
>with a -1 size for some reason.
>
>Any ideas?
>
>Thanks,
>James


-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   Gleb.Paharenko@stripped
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
       <___/   www.mysql.com