On Dec 2, 2008, at 7:21 AM, David Avendasora wrote:
Shouldn't EOF recognize that the tables are in two different
databases and not try to do one select statement that "joins" them?
If I have EntityA in database 1, and EntityA in database 2, and a
relationship between them, and try to do a fetch whose qualifier
crosses the relationship it will fail.
We run into this a lot because we have tables in many different
Oracle schemas.
I think Mike had some ideas about a possible patch for this, but
then again I seem to remember the result was to run away.
There is no real "patch" for this ... You can make it not fail, but
you'll never really make it "nice". My idea for it stems from the
work i did on the IMAP EOF Adaptor, where you have a problem along of
a similar type, which is that IMAP supports evaluating SOME types of
qualifiers on the server, but not the full set of EO qualifiers. To
expose a nice interface to IMAP, you have to basically write a join
system in-memory that has pluggable optimizers of which some can be
implemented on the server and some in-memory with post processing. I
actually have a bunch of pieces of this laying around, but nothing
that made it into a final form, but this is another one that can
definitely be done, it's just going to be ugly.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
