automigration shouldn't drop/create tables
Reported by jmoses | January 5th, 2008 @ 11:19 AM
I don't think that automigration should drop and re-create tables.
As a brand spanking new DataMapper user, this certainly wasn't the behavior I was expecting, not was it mentioned anywhere that I could find.
I had expected something called "auto" migration to compare the current state of my tables to the current state of the model and "ALTER" the tables accordingly.
This should be fixed/updated if I'm correct as to how it should work, or at least some sort of documentation change or warning should be generated.
Comments and changes to this ticket
-
-
Sam Smoot January 5th, 2008 @ 11:20 AM
- State changed from “new” to “invalid”
Nope, you've got it exactly. That's the eventual plan. For right now, it's more of something to run in your specs though.
Please add further comments to: http://wm.lighthouseapp.com/proj...
-
Dan Kubb (dkubb) April 15th, 2008 @ 03:26 AM
- no changes were found...
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 »
Dan Kubb (dkubb)
Rick