error code 139 innodb

We have an InnoDB table on MySQL 5.0.
We recently encountered an this error during a multirow insert(200 rows).
We identified the data causing it and it's a a series of long strings
exceeding the VARCHAR(255) columns into which they're being inserted.
I've been looking at the InnoDB restriction page in the manual and
nothing seems to make sense.

For sure all of our columns combined do not exceed 64K. We're using
latin 1 character set.
I don't think we would be running into the 8K limit on row length
since the culprit seems to be data being inserted into VARCHAR(255)
column.
I'm assuming MySQL is silently truncating the string as it's being
inserted into the VARCHAR column.
Our TEXT columns are empty.

Anyone have any idea what might be causing it?
Kyong

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: error code 139 innodb

Kyong Kim gmail.com> writes:

> For sure all of our columns combined do not exceed 64K. We're using
> latin 1 character set.
> I don't think we would be running into the 8K limit on row length
> since the culprit seems to be data being inserted into VARCHAR(255)
> column.

Can you show us your "create table"?

This might be a known bug http://bugs.mysql.com/bug.php?id=25945



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: error code 139 innodb

Raj,
Yup. It's that bug.
I got the row size to below 8K and the insertion takes place fine.
Thanks for pointing me in the right direction.
Kyong

On Wed, Oct 14, 2009 at 10:31 AM, Raj Shekhar wrot=
e:
> Kyong Kim gmail.com> writes:
>
>> For sure all of our columns combined do not exceed 64K. We're using
>> latin 1 character set.
>> I don't think we would be running into the 8K limit on row length
>> since the culprit seems to be data being inserted into VARCHAR(255)
>> column.
>
> Can you show us your "create table"?
>
> This might be a known bug http://bugs.mysql.com/bug.php?id=3D25945
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: =A0 =A0http://lists.mysql.com/mysql?unsub=3Dkykimdba@gmai=
l.com
>
>

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg