Same model with multiple databases and no EOs --a vendor "database"
Same model with multiple databases and no EOs --a vendor "database"
- Subject: Same model with multiple databases and no EOs --a vendor "database"
- From: Greg Brown <email@hidden>
- Date: Mon, 24 Feb 2014 08:10:10 -0500
I have a given database I want to integrate into some existing webobjects info systems.
The database is not too normal, so some directions to proceede would be appreciated.
Q1. Some tables have no primary key, so no EOs. But there is a method called rawRowsForSQL on the EOUtilities class. Is that the best option other than raw sql? All other tables have non-numeric primary keys , columns which really should be entity attributes and not primary keys. Wonder has er.extensions.eof.ERXEOAccessUtilities; any other things I should look at for raw row non-EO fun? raw SQL?
Q2. There is what I would consider a location attribute, but instead of making it an attribute, it is used as a database name. So there is one model, but several databases, all similar except for the connection dictionary. The dictionaries only differ slightly:
jdbc:postgresql://localhost:5432/locationA << (At least postgres is involved.)
VS
jdbc:postgresql://localhost:5432/locationB
EnterpriseObjects.pdf discusses:
How does an EOObjectStoreCoordinator determine which of its EOCooperatingObjectStores should service a particular fetch specification? Remember that within an EOModelGroup, entity names must be unique. Also remember that fetch specifications are entity-centric—every fetch specification is specified on the basis of a particular entity. So an object store coordinator simply looks for the list of entities registered within its cooperating object stores to match an entity name to particular cooperating object store.
So I need to setup a EOObjectStoreCoordinator (OSC) for each different database, and change the connection dictionary so it has the correct jdbc url:
jdbc:postgresql://localhost:5432/locationA << default with model
jdbc:postgresql://localhost:5432/locationB
jdbc:postgresql://localhost:5432/locationC
On these OSCs, I can use EODatabaseContext.forceConnectionWithModel to set the correct connection dictionary, or EOUtilities.connectWithModelNamed, or some other method somebody (not me) knows of. Then I just use ECs from the correct OSC to do the raw row non-EO fun:
EOObjectStoreCoordinator locationBObjectStore = new EOObjectStoreCoordinator();
EOEditingContext editingContextLocationB = new EOEditingContext(locationBObjectStore);
Does this sound like the correct direction to deal with these databases?
refs:
Re: Different Database Connection per session for the same model
site:lists.apple.com goat herding
What could go wrong?
Thanks,
Greg Brown
email@hidden
_______________________________________________
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