-
Arun Kuruvila authored
THAT FAILS FK CHECK IN FED TABLE Description: A HANDLER within a stored procedure which catches foreign key failures is currently not possible if the table involved is using FEDERATED storage engine. Analysis:- Remote server errors such as ER_NO_REFERENCED_ROW and ER_NO_REFERENCED_ROW_2 are not handled inside ha_federated::stash_remote_error() which in turn makes a stored procedure impossible to define a HANDLER that will catch a foreign key failure due to the error, "Cannot add or update a child row: a foreign key constraint fails" Fix: ER_NO_REFERENCED_ROW and ER_NO_REFERENCED_ROW_2 are handled correctly in ha_federated::stash_remote_error`().
Arun Kuruvila authoredTHAT FAILS FK CHECK IN FED TABLE Description: A HANDLER within a stored procedure which catches foreign key failures is currently not possible if the table involved is using FEDERATED storage engine. Analysis:- Remote server errors such as ER_NO_REFERENCED_ROW and ER_NO_REFERENCED_ROW_2 are not handled inside ha_federated::stash_remote_error() which in turn makes a stored procedure impossible to define a HANDLER that will catch a foreign key failure due to the error, "Cannot add or update a child row: a foreign key constraint fails" Fix: ER_NO_REFERENCED_ROW and ER_NO_REFERENCED_ROW_2 are handled correctly in ha_federated::stash_remote_error`().
Loading