Bug #20456 Field rename is not supported as fast alter table in ndbcluster
Submitted: 14 Jun 2006 10:01 Modified: 15 Jun 2006 10:37
Reporter: Martin Skold Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.1 OS:
Assigned to: Martin Skold CPU Architecture:Any

[14 Jun 2006 10:01] Martin Skold
In 5.1 a field rename is done as a fast (non-copying) alter table.
In ndbcluster there is a local data dictionary dependent on have
correct names of fields when accessed directly from NDB API.

How to repeat:
Rename a field and try to use it from an application
using NDB API.

Suggested fix:
Add a flag so that the ndbcluster handler can
detect name change in method check_if_incompatible_data
and return that table should be copied.
[15 Jun 2006 10:37] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Documented bugfix in 5.1.12 changelog; closed.