Re: Multiple Models, Coalesced Transactions - is it possible?
Re: Multiple Models, Coalesced Transactions - is it possible?
- Subject: Re: Multiple Models, Coalesced Transactions - is it possible?
- From: Mike Schrag <email@hidden>
- Date: Wed, 30 Jun 2010 08:16:09 -0400
EOF currently doesn't do any 2PC.
ms
On Jun 29, 2010, at 11:28 PM, Karl wrote:
> Does WO / EOF implement its own form of TPC or is it a case of buyer-be-aware / technology stack dependent?
>
> Karl
>
> On 2010-06-29, at 11:26 PM, Mike Schrag wrote:
>
>> These are in the same EOEditingContext transaction, but they're not in a single database transaction ... EOF does not (currently) use JTA across connections in multiple databases.
>>
>> ms
>>
>> On Jun 29, 2010, at 11:12 PM, Farrukh Ijaz wrote:
>>
>>> On 2010-06-30, at 5:56 AM, 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.
>>>>
>>>
>>> As far as I heard (may be wrong), it's possible to have EOModels connecting to different databases. They have to fall under the same EOModelGroup only then it can be treated under single transaction. (Correct me if I'm wrong).
>>>
>>> For each model, the jdbc connection properties can be setup individually.
>>>
>>> dbConnectURLGLOBAL
>>> dbConnectUserGLOBAL
>>> dbConnectPasswordGLOBAL
>>>
>>> I don't remember but I guess they are used like
>>>
>>> dbConnectURL.Model1
>>> dbConnectUser.Model1
>>> dbConnectPassword.Model1
>>>
>>> Or something similar. Someone experienced out there can point out the exact properties.
>>>
>>> Farrukh
>>>
>>>> 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?
>>>>
>>>> cheers.
>>>>
>>>> ___
>>>> Andrew Lindesay
>>>> www.silvereye.co.nz
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>> _______________________________________________
>>> 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
>>
>> _______________________________________________
>> 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
>
_______________________________________________
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