#1538: Can't execute generate-migrations-db migrations
---------------------+------------------------------------------------------
  Reporter:  jtaal   |       Owner:  jwage                
      Type:  defect  |      Status:  reopened             
  Priority:  major   |   Milestone:  1.0.4                
 Component:  Tasks   |     Version:  1.0.2                
Resolution:          |    Keywords:                       
  Has_test:  0       |    Mystatus:  Pending Core Response
 Has_patch:  0       |  
---------------------+------------------------------------------------------
Changes (by jwage):

  * milestone:  1.0.3 => 1.0.4

Comment:

 The generating migrations from db is used to generate a set of migration
 classes that will rebuild your existing database so that you can begin
 altering the database with new manually written migration classes. Since
 you already have the migration_version table in your database when you run
 generate-migrations-db it creates the migration_version class which tries
 to create that table when you run the migrate process. Doctrine migrations
 automatically create that table and keep it updated with the version
 number so it already exists by the time that migration class is executed.

 Though this is a problem that can be fixed by just deleting that
 migration_version class and then running the migrate command will work. I
 think we should fix the migration generator to be smart enough to skip the
 migration_version when it comes across it.

-- 
Ticket URL: <http://trac.doctrine-project.org/ticket/1538#comment:7>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"doctrine-svn" group.
 To post to this group, send email to [email protected]
 To unsubscribe from this group, send email to [EMAIL PROTECTED]
 For more options, visit this group at 
http://groups.google.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---

Reply via email to