#4396 (ok 4.2.3) Problem copying constraints (such as Sakila)

4.2.1
fixed
None
1
2014-06-08
2014-05-10
No

As reported by J.M., there is a problem when copying databases with constraints in some cases. For instance, trying to duplicate the sakila database gives this message:

ALTER TABLE address
ADD CONSTRAINT fk_address_city FOREIGN KEY (city_id) REFERENCES city (city_id) ON UPDATE CASCADE;

8cf74b688d882a9545a651498664de912c7fb659 is the first bad commit.

Discussion

  • Marc Delisle

    Marc Delisle - 2014-05-18
    • Group: 3.3.7 --> 4.2.1
     
  • Viduranga Wijesooriya

    Hi,

    "ALTER TABLE address
    ADD CONSTRAINT fk_address_city FOREIGN KEY (city_id) REFERENCES city (city_id) ON UPDATE CASCADE;"
    This is not an error message. Isn't that ?

    I believe this is the error.
    "#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '.actor MODIFY actor_id smallint( 5 ) unsigned NOT NULL AUTO_INCREMENT ' at line 1"

    Can you confirm ?

     
  • Marc Delisle

    Marc Delisle - 2014-05-31
    • assigned_to: Marc Delisle
     
  • Marc Delisle

    Marc Delisle - 2014-05-31

    I am able to reproduce this in 4.2.1, but it has been fixed in 4.2.2 along with another bug fix. I'm marking this fixed for 4.2.3 as 4.2.2 has already been released.

     
  • Marc Delisle

    Marc Delisle - 2014-05-31
    • summary: Problem copying constraints (such as Sakila) --> (ok 4.2.3) Problem copying constraints (such as Sakila)
    • status: open --> resolved
    • Priority: 5 --> 1
     
  • Marc Delisle

    Marc Delisle - 2014-06-08
    • Status: resolved --> fixed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks