• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: modify the db from EOModel without risking the data
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: modify the db from EOModel without risking the data


  • Subject: Re: modify the db from EOModel without risking the data
  • From: WebObjects <email@hidden>
  • Date: Thu, 16 Oct 2008 10:01:30 -0500

WOW I didn't realize that one. oops my big mistake thats what happens when you have headache.
Fixing it. Im gonna give a loot at migrations (so I don't have to change directly form the db).. I don't remember why I didn't use it, oh yes I remember now, because I was having problem with frontbase,(I think the one its being discussed on the last days) but now that Im with openBase Im gonna look and see if that works.



Gus.




On Oct 16, 2008, at 8:23 AM, David Avendasora wrote:

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
References: 
 >modify the db from EOModel without risking the data (From: WebObjects <email@hidden>)
 >Re: modify the db from EOModel without risking the data (From: David Avendasora <email@hidden>)

  • Prev by Date: Re: EO Caching with global id 'fetching'
  • Next by Date: Re: EO Caching with global id 'fetching'
  • Previous by thread: Re: modify the db from EOModel without risking the data
  • Next by thread: I dont get it, still nullpointer exception
  • Index(es):
    • Date
    • Thread