when db schema changes... al goes wrong
when db schema changes... al goes wrong
- Subject: when db schema changes... al goes wrong
- From: Gustavo Pizano <email@hidden>
- Date: Sat, 8 Aug 2009 20:01:25 +0200
Hello, long time without posting any question, I was assigned a iphone
project, and now back to WO.
Here at work decided to change the db schema, and add some more table
and relationships, but they are not new apart from the ones I had
already, they actually will touch the schema I was working on and the
logic I was working with.
So, pain in the behind!!!! for me.
Im using migrations, this should work for something no?, when I create
the new migration page then it complains that everything already
exists!, and I can't delete anything otherwise.. all data goes to hell.
then I dunno if my design is that poor or what but I will have to
touch the components that were doing something in the db in that
specific area that its gonna be modified... so to keep avoiding this
problems inthe future what suggestions you may have for me....
I wanna cry I have to arrive on monday and start working on those
changes, I was just todl today that they are waiting for me... great
bday present I will have at the office on monday,
G.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden