Add / removing indices causing missing rows
Posted by:
John Ewing
Date: April 26, 2007 08:06AM
I had a problem recently with Mysql 4.1.22 merge tables where a collegue did an
altereration to an indice of one of the underlying tables. The net result
was that the two tables in the union statment had the same indices but in a different order.
The first we noticed a problem was when some queries started returning odd results. Browsing the merge tables showed that certain rows which
existed in the underlying tables weren't showing up in the merge table.
Droping and recreating the indices so that all three tables had the same indice order fixed this.
My question is this.
Shouldn't the correct behavior in this situation be to throw an error when you try to access the merge table instead of silently returning erroneous results?
Thanks
J.
Subject
Views
Written By
Posted
Add / removing indices causing missing rows
8692
April 26, 2007 08:06AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.