Reset migrations
Reported by Guilherme Chapiewski | February 13th, 2009 @ 10:05 PM | in BACKLOG
Reset functionality: drop all tables (don't drop database) and migrate to the latest version (remember to drop views first).
This would be useful for databases where the user doesn't have rights to drop and re-create the database but just the tables.
Comments and changes to this ticket
-
Guilherme Chapiewski February 27th, 2009 @ 01:36 AM
- Milestone changed from “BACKLOG” to “v1.2.0”
-
Guilherme Chapiewski March 12th, 2009 @ 01:20 AM
- Milestone changed from “v1.2.0” to “v1.4.0”
Moving to 1.3 because it's not that important considering ticket #22 is implemented.
-
Bernardo Heynemann July 14th, 2010 @ 05:54 PM
- Milestone changed from “v1.4.0” to “BACKLOG”
- Milestone order changed from “0” to “0”
-
Guilherme Chapiewski July 15th, 2010 @ 12:03 PM
Another scenario: you have a lot of user rights set up in your database, but for security reasons, the users are not being created in the db-migrate scripts (you don't want the passwords open in a text file). Then if you drop database, you will lose this setup, so it would be better to drop and re-create everything.
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/
Bernardo Heynemann
Guilherme Chapiewski