Connecting to multiple databases through model via fetch specification problems.
Connecting to multiple databases through model via fetch specification problems.
- Subject: Connecting to multiple databases through model via fetch specification problems.
- From: Olav Anderson <email@hidden>
- Date: Sun, 19 Dec 2004 18:03:12 -0800
Hi,
Has anyone successfully resolved queries via EOModels across multiple
databases using fetchspecifiations?
I have two databases and two models with relationships defined to fetch
data from the second database when a relationship is resolved.
e.g.
TPS DB TPSStorageDB
----------- --------------------
TPSReport -> TPSChannel
Running the WO app it has no problem resolving the relationship across
the databases via normal kvc, I can get all the TPSChannels from the
TPSStorageDB for the TPSReport no problem.
The problem occurs when I construct a fetch specification or do a
rawRows fetch I get an error expression failed semantic error table
TPSReport does not exist when I want to find all the TPSReports for a
TPSChannel.
I've constructed the fetch specifications through the EOModel GUI,
programatically, every way possible.
I was wondering if anyone has had success with this over and above the
vanilla resolving of relationships through key path/faults?
As soon as I combine the databases into one database all the problems
go away, of course, but, I would like to split the data into distinct
databases if possible and have been looking into this for a while to
see if I am missing something obvious but, now I am at a loss.
Any ideas?
Thanks,
Olav
_______________________________________________
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