bug#30337 DELETE ... WHERE PK IN (..) and AFTER DELETE trigger crashes API...

bug#30337  DELETE ... WHERE PK IN (..) and AFTER DELETE trigger crashes API node: Disable multi_read_range if there are after delete/update triggers
parent 3afa32dc
...@@ -6464,7 +6464,8 @@ ha_ndbcluster::read_multi_range_first(KEY_MULTI_RANGE **found_range_p, ...@@ -6464,7 +6464,8 @@ ha_ndbcluster::read_multi_range_first(KEY_MULTI_RANGE **found_range_p,
if (uses_blob_value(m_retrieve_all_fields) || if (uses_blob_value(m_retrieve_all_fields) ||
(cur_index_type == UNIQUE_INDEX && (cur_index_type == UNIQUE_INDEX &&
has_null_in_unique_index(active_index) && has_null_in_unique_index(active_index) &&
null_value_index_search(ranges, ranges+range_count, buffer))) null_value_index_search(ranges, ranges+range_count, buffer))
|| m_delete_cannot_batch || m_update_cannot_batch)
{ {
m_disable_multi_read= TRUE; m_disable_multi_read= TRUE;
DBUG_RETURN(handler::read_multi_range_first(found_range_p, DBUG_RETURN(handler::read_multi_range_first(found_range_p,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment