MySQL Forums
Forum List  »  Merge Storage Engine

Re: Altering merge table immediately after creation throws error
Posted by: Ingo Strüwing
Date: March 14, 2007 02:14PM


Why do you need to add the second columns in separate ALTER statements? Why not just CREATE the table with both columns from the beginning?

There have been a number of bugs around MERGE table compatibility. Bug report #457 contains a list:

The mentioned worklog has the title "MERGE engine: a check for underlying table conformance". Its resulting effect is documented in
Search for the section starting with "In MySQL 5.1.15 and later, when a table that is part of a MERGE table is opened, the following checks are applied".

Unfortunately, there are new issues, which require more work:

If you think that none of the problems match yours and the latest versions don't fix it, please report it on


Ingo Strüwing, Senior Software Developer - Storage Engines

Options: ReplyQuote

Written By
Re: Altering merge table immediately after creation throws error
March 14, 2007 02:14PM
May 03, 2008 07:24PM

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.