>> the table becomes corrupted. Is this some limitation of inno DB or should I
>> separate the UPDATE process in two separate UPDATE statements?
>It's a known and confirmed bug that will be fixed in 3.23.42. There
>was an announcement just posted about this a few minutes ago.
Hi Jeremy,
thanks
On Sun, Aug 26, 2001 at 09:10:31PM +0200, Ralph Graulich wrote:
> Hi,
>
> recently I converted a table containing a large amount of text
> fields from myISAM to inno-DB and encountered a problem I can't help
> with. The table structure consists of:
>
> textref_id INT(12) UNSIGNED
>
Hi,
recently I converted a table containing a large amount of text fields from
myISAM to inno-DB and encountered a problem I can't help with. The table
structure consists of:
textref_id INT(12) UNSIGNED
textref_cat_id INT(12) UNSIGNED
textgroup_key CHAR(5) NOT NU
