Re: modify the db from EOModel without risking the data
Re: modify the db from EOModel without risking the data
- Subject: Re: modify the db from EOModel without risking the data
- From: David Avendasora <email@hidden>
- Date: Thu, 16 Oct 2008 09:23:45 -0400
You are getting closer!
Okay, now the relationships are right in terms of their to-one/to-many
type, BUT - and this is a HUGE BUT - you have the source and
destination attributes wrong for every relationship.
Here's how they should be:
Employee.id <->> EmployeeXTurn.employeeID
Turn.id <->> EmployeeXTurn.turnID
You need to change both sides of the relationships. They are all wrong.
On simply cosmetic notes:
1) The turns relationship on EmployeeXTurn should be named "turn" as
it is a to-one relationship.
2) Since the EmployeeXTurn entity isn't just a join table, but
contains actual business information, I would consider simply calling
it "EmployeeTurn", especially since that describes perfectly what it
is a list of Employees and their turns.
Dave
On Oct 15, 2008, at 8:45 PM, WebObjects wrote:
Hello, well after making the chances of my EOModel. when it came to
change the db as well I came to the question on how to change the db
squema, which were only modify some relationships, without deleting
the data?
what I did was that I made the changes on EOModel as well directly
on the db via openbase.
any suggestions?......
btw.. David and Dave here is db with the relationship fixed I wish
this time its fine.
;-)
<ScheduleControl.eomodeld>
_______________________________________________
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
_______________________________________________
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