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?
The version I use is 3.32.41, linux, 2.2.19 kernel, gcc 2.95.2. If needed,
I can provide a mysqlbugreport.
With my best regards
... Ralph ...
---------------------------------------------------------------------
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
