On Jun 29, 2010, at 7:56 PM, Andrew Lindesay wrote:

> Hello;
> 
> I have 5-6 models in an application.  Thus far this has worked out fine 
> because many database servers were employed and a socket or two to each was 
> not a problem.  Now the database servers have been consolidated and with each 
> model requiring a database connection, the number of connections to one 
> database server from all of the instances is actually quite large!
> 
> I have been reading the java-doc for the JDBC*/EO* classes trying to get my 
> head around how things work at the JDBC connection / transaction level.  What 
> I would like to do is to modify the "Table Name" in the models to be prefixed 
> with the schema name and then to somehow see if I could use one connection 
> and hence coalesce each transaction commit/rollback across all of the models.
> 
> My guess is that this concept is not how EOF works and I'm probably not going 
> to be able to do it without also coalescing the models together.
> 
> Has anybody any insights?


Are these models using different logins and schemas?  If not, they should all 
share the same connection if their connection dictionaries are .equals().  If 
they are all different, then EOF is going to want to consider them to be 
different.  Putting the schema name in the table name and ensuring that the 
connection dictionaries are .equals() may work, I have never tried that.


Chuck


-- 
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall 
knowledge of WebObjects or who are trying to solve specific problems.    
http://www.global-village.net/products/practical_webobjects







Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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]

Reply via email to