Bug #31348 | MERGE fails with 'not identical' in V5.0.45 | ||
---|---|---|---|
Submitted: | 2 Oct 2007 17:17 | Modified: | 3 Oct 2007 18:02 |
Reporter: | Dave Pullin (Basic Quality Contributor) | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.45 | OS: | Linux (and Windows 2Ksvr) |
Assigned to: | CPU Architecture: | Any | |
Tags: | qc |
[2 Oct 2007 17:17]
Dave Pullin
[3 Oct 2007 10:40]
Valeriy Kravchuk
Thank you for a problem report. Please, send the results of: SHOW CREATE TABLE bug_model;
[3 Oct 2007 13:15]
Dave Pullin
Sorry - my mistake: Although 5.0.27 considers these two tables to be identical and will perform a MERGE on them, they are not in fact identical, so V5.0.45 is correct in rejecting the merge. One of the columns was changed from NOT NULL to DEFAULT NULL - but that is my bug not yours. Therefore this is NOT A BUG, unless you consider V5.0.27 NOT rejecting the merge to be an issue.
[3 Oct 2007 18:02]
Valeriy Kravchuk
Looks like it is not a bug in 5.0.45.