Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#3446 Relation is lost after copying a table

3.4.5
out-of-date
Marc Delisle
5
2013-06-11
2011-10-04
Anonymous
No

When performing a copy of the table from one DB to another, the structure and data is transferred without any problems, nevertheless foreign keys are lost. This is understandable behaviour, since the table might not exist in the new DB, so it might worth it to check if related table exists first, and warn if keys can not be recreated. Also, there is no option to copy selected tables from one DB to another - either all, or one by one. Pretty annoying if you want to duplicate just 10 tables out of 100.

Discussion


  • Anonymous
    2011-10-04

    • summary: Copying table relation is lost --> Copying table, relation is lost
     

  • Anonymous
    2011-10-04

    • summary: Copying table, relation is lost --> Relation is lost after copying a table
     
  • Marc Delisle
    Marc Delisle
    2011-11-26

    Version 3.4.5 is old. In the current 3.4.7 version, in the copy table dialog, you have a "Add constraints" option.

    For your other question, have a look at the Synchronize feature.

     
  • Marc Delisle
    Marc Delisle
    2011-11-26

    • assigned_to: nobody --> lem9
    • status: open --> pending-out-of-date
     
  • Marc Delisle
    Marc Delisle
    2013-01-18

    • status: pending-out-of-date --> closed-out-of-date
     
  • Michal Čihař
    Michal Čihař
    2013-06-11

    • Status: closed-out-of-date --> out-of-date