Re: error code 139 innodb

2009-10-15 Thread Kyong Kim
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 wrote: > Kyong Kim gmail.com> writes: > >> For sure all of our columns combined do not exceed 64K. We're

Re: error code 139 innodb

2009-10-14 Thread Raj Shekhar
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 "cr

error code 139 innodb

2009-10-12 Thread Kyong Kim
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 pag