It seems this issue will be fixed in 4.0.13, I filed a bug and it was closed with this report:

Sinisa Milivojevic:

Yes, this is a known problem.
It is already fixed in 4.0.13, which will come out this month.

This is a patch:

===== sql/sql_update.cc 1.79 vs 1.80 =====
*** /tmp/sql_update.cc-1.79-11704       Wed Mar 19 00:45:43 2003
--- 1.80/sql/sql_update.cc      Wed Apr  2 17:05:30 2003
***************
*** 741,747 ****
         (error != HA_ERR_FOUND_DUPP_KEY &&
          error != HA_ERR_FOUND_DUPP_UNIQUE))
       {
!       if (create_myisam_from_heap(table, tmp_table_param + offset,
error, 1))
       {
         do_update=0;
         DBUG_RETURN(1);                       // Not a table_is_full
error
--- 741,747 ----
         (error != HA_ERR_FOUND_DUPP_KEY &&
          error != HA_ERR_FOUND_DUPP_UNIQUE))
       {
!       if (create_myisam_from_heap(tmp_table, tmp_table_param +
offset, error, 1))
       {
         do_update=0;
         DBUG_RETURN(1);                       // Not a table_is_full
error


Cheers,


-- =={Gerrit Hannaert}==

IT Department, CropDesign N.V.


-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to