Bug #54279 | failing compatibility checks in ndb_restore attribute promotion | ||
---|---|---|---|
Submitted: | 7 Jun 2010 9:05 | Modified: | 18 Jun 2010 9:03 |
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.1-telco-7.1 | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | mysql-cluster-7.1.4 |
[7 Jun 2010 9:05]
Hartmut Holzgraefe
[7 Jun 2010 9:14]
Hartmut Holzgraefe
This actually seems to affect any fixed size type with a default value when going from pre-7.1.4 to 7.1.4 (or beyond), e.g. also fails with the following test table: CREATE TABLE t1 ( id int primary key, n int default 3 ) engine=ndb;
[7 Jun 2010 9:19]
Hartmut Holzgraefe
probably better solution than adding lots of new type/type comparison functions: have a new equal_enough() function instead of equal() that ignores certain column attributes like DEFAULT or DYNAMIC ...
[7 Jun 2010 9:43]
Hartmut Holzgraefe
See also bug #54242
[18 Jun 2010 9:03]
Frazer Clement
Duplicate of bug#54242. The fix for #54242 relaxes the equality checks to ignore differences in column's default values. This occurs before / independently of type promotion logic.