I developed a website, using Umbraco (umbraco v
4.0.2.1 (Assembly version: 1.0.3441.17657)). The database is MySQL, which run on one of our development servers. So far so good.
Now I try to import the backup file I made (using MySQL Administrator tool) into the webhost. But during the import, I got the following error message:
ERROR 1074 (42000) at line 1947: Column length too big for column 'EMAIL' (max = 255); use BLOB or TEXT instead
Does somebody know what the reason is about this error?
I don't use MySQL but it seems that the error is as described.
The field 'EMAIL' (I'm not sure which table) needs to be changed from whatever it is to a TEXT field as the data it is trying to import is too long for the field.
Thinking about it, there shouldn't really be anything too long in an 'Email' field so maybe your mapping is out somehow?
I can't find it anywhere but I thought the MySQL support required MySQL 5. I'll keep looking to see if I can verify that one way or the other. But to keep you moving, is there any chance you can try with MySQL 5.x?
Column length too big for column 'EMAIL'
I developed a website, using Umbraco (umbraco v 4.0.2.1 (Assembly version: 1.0.3441.17657)). The database is MySQL, which run on one of our development servers. So far so good.
Now I try to import the backup file I made (using MySQL Administrator tool) into the webhost. But during the import, I got the following error message:
ERROR 1074 (42000) at line 1947: Column length too big for column 'EMAIL' (max = 255); use BLOB or TEXT instead
Does somebody know what the reason is about this error?
I don't use MySQL but it seems that the error is as described.
The field 'EMAIL' (I'm not sure which table) needs to be changed from whatever it is to a TEXT field as the data it is trying to import is too long for the field.
Thinking about it, there shouldn't really be anything too long in an 'Email' field so maybe your mapping is out somehow?
Well, there are a lot more tables with will cause that problem. The 'EMAIL' field is a varchar(1000) and there a much more table columns with that.
By the way, our host provider run MySQL 4.1.22.
Are there more people out there, dealing with this problem?
I can't find it anywhere but I thought the MySQL support required MySQL 5. I'll keep looking to see if I can verify that one way or the other. But to keep you moving, is there any chance you can try with MySQL 5.x?
cheers,
doug.
I found a workaround. In the backup script, I changed all varchar(1000) into tinytext. As far as I can see now, it doesn't give any problems.
is working on a reply...