summaryrefslogtreecommitdiff
path: root/sql/ha_partition.h
diff options
context:
space:
mode:
authorAditya A <aditya.a@oracle.com>2013-10-21 12:07:02 +0530
committerAditya A <aditya.a@oracle.com>2013-10-21 12:07:02 +0530
commitc5896384bda582ec6f43ceb3fe9e7530e0bf819d (patch)
treeb0a6f6d23ea3ddfd431b61063168456d40c383e1 /sql/ha_partition.h
parent7a524cee32e3a7d457fa6a0e86351ddac1c219fb (diff)
downloadmariadb-git-c5896384bda582ec6f43ceb3fe9e7530e0bf819d.tar.gz
Bug #16051817 GOT ERROR 124 FROM STORAGE ENGINE
ON DELETE FROM A PARTITIONED TABLE PROBLEM ------- The user first disables all the non unique indexes in the table and then rebuilds one partition. During rebuild the indexes on that particular partition are enabled. Now when we give a query the optimizer is unaware that on one partition indexes are enabled and if the optimizer selects that index,myisam thinks that the index is not active and gives an error. FIX --- Before rebuilding a partition check whether non unique indexes are disabled on the partitons. If they are disabled then after rebuild disable the index on the partition. [Approved by Mattiasj #rb3469]
Diffstat (limited to 'sql/ha_partition.h')
-rw-r--r--sql/ha_partition.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/sql/ha_partition.h b/sql/ha_partition.h
index eef93e056ef..153e610d86f 100644
--- a/sql/ha_partition.h
+++ b/sql/ha_partition.h
@@ -270,7 +270,8 @@ private:
void cleanup_new_partition(uint part_count);
int prepare_new_partition(TABLE *table, HA_CREATE_INFO *create_info,
handler *file, const char *part_name,
- partition_element *p_elem);
+ partition_element *p_elem,
+ uint disable_non_uniq_indexes);
/*
delete_table, rename_table and create uses very similar logic which
is packed into this routine.