Re: Help Please: Problem with Insert in Chapter 10 of Web Applications Tutorial
Re: Help Please: Problem with Insert in Chapter 10 of Web Applications Tutorial
- Subject: Re: Help Please: Problem with Insert in Chapter 10 of Web Applications Tutorial
- From: Art Isbell <email@hidden>
- Date: Fri, 10 Oct 2003 12:30:48 -1000
On Friday, October 10, 2003, at 07:51 AM, Chuck Hill wrote:
This is a perfect example why you should always use EOPrototypes. They
make such changes nearly painless.
One cause of pain when using EOPrototypes is that "EOPrototypes" is an
entity name. Like other entity names, it must be unique in any
EOModelGroup (i.e., in all eomodels loaded into a process). So if you
use or might use multiple eomodels in an application, you cannot have
an EOPrototypes entity in each model.
I think I have run into other pains using EOPrototypes as well. I
can't recall the details, but I think what happened was that I had an
eomodel that used EOPrototypes defined in a different eomodel. Maybe I
then tried to use this eomodel in an app without the eomodel that
included EOPrototypes. I think this resulted in attributes not being
completely defined causing run-time exceptions.
Because of these pains, I quit using EOPrototypes, but maybe I didn't
try hard enough :-) Maybe a workaround for these problems would be to
define an eomodel with a single entity, EOPrototypes. This eomodel
would be in a custom framework loaded by every custom application.
Anyone tried this? Any other workarounds for these problems?
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.