Re: Dealing with relationships and inheritance

2008-02-08 Thread David Holt
Hi Philippe, Practical WebObjects uses Eclipse, but there have been a lot of improvements to the WOLips tools since it was published. It is intended for a pretty experienced audience, but the concepts are very valuable to start to wrap your head around even if you're a beginner. Check o

Re: Dealing with relationships and inheritance

2008-02-08 Thread Philippe Guitard
As far as I know there's no book covering WebObjects programming with WOLips. Would Chuck's book "Practical WebObjects" be a good starting point to learn the WO concepts with the IDE set aside (XCode vs. Eclipse)? ~Philippe ___ Do not post admin request

Re: Dealing with relationships and inheritance

2008-02-08 Thread Chuck Hill
I was fairly sure that I have seen this in other situations, but it might just have been using the EOUtilities methods which don't set isDeep. Charles, are your table names identical in the model? What code is triggering the multiple selects on one table? Chuck On Feb 7, 2008, at 3:22

Re: Dealing with relationships and inheritance

2008-02-07 Thread Mike Schrag
I got burned by this back in 2005 (there's a thread from 2005 where Chuck and I discuss this problem -- isDeep = false also means that cache in memory is bypassed) http://lists.apple.com/archives/webobjects-dev/2005/May/msg00356.html ms ___ Do not

Re: Dealing with relationships and inheritance

2008-02-07 Thread Mike Schrag
So it appears (if I'm reading this code properly) that EOF merges restricting qualifiers for single table inheritance. In EOSQLExpression, if the fetch spec .isDeep() and if the entity._isSingleTableEntity(), then it will merge the restricting qualifiers together into a big EOOrQualifier (

Re: Dealing with relationships and inheritance

2008-02-07 Thread Mike Schrag
Any advice? That it the way it is. I don't know how easy it would be to optimize these. EOF might expect there to be only a single entity per result set. I was pretty sure I was not seeing this behavior, so I verified it in one of our apps: to-many fault: 2008-02-07 16:14:27,535 DEBUG

Re: Dealing with relationships and inheritance

2008-02-07 Thread Mr. Pierre Frisch
I would suggest to take a look at EODatabaseContext.Delegate. In particular: public NSArray databaseContextShouldFetchObjects(EODatabaseContext dbCtxt, EOFetchSpecification fetchSpec, EOEditingContext ec); Cheers Pierre -- Pierre Frisch [EMAIL PROTECTED] On Feb 7, 2008, at 13:02, Chuck

Re: Dealing with relationships and inheritance

2008-02-07 Thread Chuck Hill
On Feb 7, 2008, at 12:32 PM, Charles Koppelman wrote: We've been using single-table inheritance here for quite a while. Let's start with an example: A person can send an email or fax. They share plenty of fields and plenty of methods, but there is a bit of divergence. So we have something l