Hi. I have encountered a MySQL 4.0.18 (Fedora Core 1) innodb problem which has been confirmed by the developers.
If I define 16 consecutive text, mediumtext, or longtext fields, when the size of data exceeds 8000bytes, table updates fail (1030, 'Got error 139 from table handler). >From the MySQL developers: >> "this is probably not a bug. InnoDB stores the first >> 512 bytes of TEXT/BLOB to the row, and the max >> length of a row is 8000 bytes." Based on my disccusions with some MySQL programmers, this feature is not going to be fixed anytime soon. I have the need to store 18 less than 64K chunks of text sequentially, yet not generate this unacceptable error. The application is large and complicated enought that breaking tables into two (or on some cases more) sub-tables significantly added to the logic overhead (would require many joins). Are there any workarounds for this, or alternative text types for storing 64K of text, but not as a blob? Harlow Pinson Indepth Learning Email: [EMAIL PROTECTED] Web: http://www.indepthl.com Voice: 505-994-2135 FAX: 208-475-7678 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
