Below is the list of changes that have just been committed into a local
5.0 repository of marty. When marty does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html
ChangeSet@stripped, 2007-08-13 11:36:30+02:00, mskold@stripped +1 -0
bug#30337 DELETE ... WHERE PK IN (..) and AFTER DELETE trigger crashes API node:
Disable multi_read_range if there are after delete/update triggers
sql/ha_ndbcluster.cc@stripped, 2007-08-13 11:35:52+02:00, mskold@stripped +2 -1
bug#30337 DELETE ... WHERE PK IN (..) and AFTER DELETE trigger crashes API node:
Disable multi_read_range if there are after delete/update triggers
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: mskold
# Host: linux.site
# Root: /windows/Linux_space/MySQL/mysql-5.0-ndb
--- 1.314/sql/ha_ndbcluster.cc 2007-08-13 11:36:40 +02:00
+++ 1.315/sql/ha_ndbcluster.cc 2007-08-13 11:36:40 +02:00
@@ -6464,7 +6464,8 @@ ha_ndbcluster::read_multi_range_first(KE
if (uses_blob_value(m_retrieve_all_fields) ||
(cur_index_type == UNIQUE_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;
DBUG_RETURN(handler::read_multi_range_first(found_range_p,
| Thread |
|---|
| • bk commit into 5.0 tree (mskold:1.2473) BUG#30337 | Martin Skold | 13 Aug |