Hallo Susanne;
This is where a one-way replica of a database is used for batch
processing. I think the problem I was having was that the
"EntityLoadedNotification"-s were flying around and possibly making
the wrong associations with models. If I fully load the models first
then this seems to stop being a problem. I'm interested; do you
encode the EOEntity from model A into a property list and then fiddle
the property list and then deserialise it into the second model?
cheers.
we are hassling with models here a lot, but with a mix of the
procedure you discribed and the one of Chuck. Instead of reloading
model B we are copying model A to a new model B with renaming the
entities while copying. For normal work both models are put into
the default model group. For rare occasions we need real duplicates
(same entity names) to a different database scheme and then put the
duplicate models into a separate model group.
Were you just curious or do you have a concrete problem with this?
...
I'm doing;
1) fully-load model A
2) set the JDBC config for model A
3) re-load clone model into a new EOModel called B from A's URL
4) rename B's entities and the model with a suffix "RO".
5) make B's entities read-only
6) insert B into the default model group
This allows me to force some database queries to a separate server
as long as there is no "crossing-of-the-models". Has anybody
else tried something like this?
___
Andrew Lindesay
technology : www.lindesay.co.nz
business : www.silvereye.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
