Re: One Login EOModel for multiple apps?
Re: One Login EOModel for multiple apps?
- Subject: Re: One Login EOModel for multiple apps?
- From: Art Isbell <email@hidden>
- Date: Tue, 8 Jul 2003 07:32:01 -1000
On Tuesday, July 8, 2003, at 03:53 AM, james o wrote:
-in EOModeler, how do i make relationships from the new Login Database
to my other EOModels?
When creating a new relationship, the destination attribute browser in
the Relationship Inspector should include a Model pop-up button listing
the various eomodels available.
-from what i've read in the lists, EOF handles all of the new to-one
and to-many relationships. is this true? any gotchas?
Relationships across databases require special consideration if the
database doesn't support such relationships. Basically, you can't
create any fetch that will result in a join across databases.
-does EOF lock the login object from any app referencing the Login
table? can the other apps referencing this object see that it's
locked? it seems like locking could get very complicated if two
people are editing the same object concurrently.
By default, EOF uses optimistic locking which means that a portion of
the database isn't explicitly locked by one user. Any conflicts will
result in an exception when subsequent users try to save conflicting
changes, so if this is likely, you need to catch and handle such
exceptions.
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.