[BUG] Transacional migrations
Reported by Guilherme Chapiewski | June 17th, 2009 @ 01:02 AM
Each migration has to be ATOMIC. Or you execute the WHOLE migration or nothing is executed. The actual state is that the migration commanded is splitted by ";", resulting in many commands per migration. If a migration fails in the middle the database gets in an unmanageable state and has to be recreated.
Ideas:
- Allow only one DDL or many DML per migration (because DDL has an
implicit transaction) - Search all migration files before executing
to guarantee that there is only one DDL command per migration
I don't think these ideas are very good indeed. There should be a way to solve this problem.
Comments and changes to this ticket
-
Wandenberg Peixoto April 10th, 2012 @ 12:35 AM
- State changed from “new” to “invalid”
- Milestone cleared.
- Milestone order changed from “0” to “0”
Is better to adopt the process of only put one DDL command per migration, but not force this on the tool.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
simple-db-migrate is a database migration tool inpired on Rails migrations. For more info check the project website: http://guilhermechapiewski.github.com/simple-db-migrate/
Guilherme Chapiewski
Wandenberg Peixoto