#1016 (ok 3.1.1) copy: check "Add AUTO_INCREMENT value" by default

fixed
None
1
2013-06-11
2007-03-27
No

database->operations->copy:

i think "Add AUTO_INCREMENT value" should be checked by default (as "Structure and data" already is). Otherwise one gets into trouble when trying to insert a new rows into the copied db (the least is a "Warning (1366): Incorrect integer value..." if that value already exists)

Discussion

  • Jürgen Wind

    Jürgen Wind - 2007-03-27
    • summary: check "Add AUTO_INCREMENT value" by default --> copy DB: check "Add AUTO_INCREMENT value" by default
     
  • Jürgen Wind

    Jürgen Wind - 2007-03-27

    Logged In: YES
    user_id=1383652
    Originator: YES

    ... in copy table as well of course.

     
  • Jürgen Wind

    Jürgen Wind - 2007-03-27
    • summary: copy DB: check "Add AUTO_INCREMENT value" by default --> copy: check "Add AUTO_INCREMENT value" by default
     
  • Sebastian Mendel

    Logged In: YES
    user_id=326580
    Originator: NO

    next auto_increment value is determined at runtime if not set - it is only required to set if it is different from MAX(PK)+1,

    what type of engine did you tried?
    what mysql version?

    there should not come such an error, IMHO

     
  • Jürgen Wind

    Jürgen Wind - 2007-03-27

    Logged In: YES
    user_id=1383652
    Originator: YES

    As usual i used pma.cihar.com ;)
    If one wants to copy a db he usually wants a as exact copy as possible.
    In "move" it is checked by default for the same reason.
    If you copy the strucure only it's better unchecked.

     
  • Michal Čihař

    Michal Čihař - 2007-04-26
    • assigned_to: nobody --> nijel
     
  • Michal Čihař

    Michal Čihař - 2007-04-26

    Logged In: YES
    user_id=192186
    Originator: NO

    I also thing that copy should default to exact copy.

     
  • Michal Čihař

    Michal Čihař - 2008-11-28
    • priority: 5 --> 1
    • summary: copy: check "Add AUTO_INCREMENT value" by default --> (ok 3.1.1) copy: check "Add AUTO_INCREMENT value" by default
    • status: open --> open-fixed
     
  • Michal Čihař

    Michal Čihař - 2008-11-28

    Implemented in SVN (no idea why I forgot about this issue).

     
  • Marc Delisle

    Marc Delisle - 2009-06-15
    • status: open-fixed --> closed-fixed
     
  • Michal Čihař

    Michal Čihař - 2013-06-11
    • Status: closed-fixed --> fixed
     

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

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks