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
> textref_cat_id INT(12) UNSIGNED
> textgroup_key CHAR(5) NOT NULL
> texthier_key CHAR(5) NOT NULL
> textidfc_osk CHAR(25)
> textcontent TEXT
> ... plus many other fiels, about 25
>
> The primary consists of a concatenated key "textref_id, textref_cat_id".
> According to some internal structures, the primary key may change while the
> archiving process of newer texts goes on.
>
> Whenever I issue a statement like:
>
> UPDATE fulltext_arch SET textref_id=508281, textref_cat_id=881 WHERE
> textidfc_osk='MED-ADM-20010502-067';
>
> 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.
Jeremy
--
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936
MySQL 3.23.41-max: up 9 days, processed 115,312,654 queries (140/sec. avg)
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
