• dlenev@mysql.com's avatar
    Fix for bug#18437 "Wrong values inserted with a before update trigger on · d4450e66
    dlenev@mysql.com authored
    NDB table".
    
    SQL-layer was not marking fields which were used in triggers as such. As
    result these fields were not always properly retrieved/stored by handler
    layer. So one might got wrong values or lost changes in triggers for NDB,
    Federated and possibly InnoDB tables.
    This fix solves the problem by marking fields used in triggers
    appropriately.
    
    Also this patch contains the following cleanup of ha_ndbcluster code:
    
    We no longer rely on reading LEX::sql_command value in handler in order
    to determine if we can enable optimization which allows us to handle REPLACE
    statement in more efficient way by doing replaces directly in write_row()
    method without reporting error to SQL-layer.
    Instead we rely on SQL-layer informing us whether this optimization
    applicable by calling handler::extra() method with
    HA_EXTRA_WRITE_CAN_REPLACE flag.
    As result we no longer apply this optimzation in cases when it should not
    be used (e.g. if we have on delete triggers on table) and use in some
    additional cases when it is applicable (e.g. for LOAD DATA REPLACE).
    
    Finally this patch includes fix for bug#20728 "REPLACE does not work
    correctly for NDB table with PK and unique index".
      
    This was yet another problem which was caused by improper field mark-up.
    During row replacement fields which weren't explicity used in REPLACE
    statement were not marked as fields to be saved (updated) so they have
    retained values from old row version. The fix is to mark all table
    fields as set for REPLACE statement. Note that in 5.1 we already solve
    this problem by notifying handler that it should save values from all
    fields only in case when real replacement happens.
    d4450e66
sql_load.cc 35.4 KB