You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by Brian McCallister <mc...@forthillcompany.com> on 2004/06/10 01:19:32 UTC

Optimistic Transactions, Proxies, and Locking in ODMG

I am trying to figure out (and document!) proxy and locking behavior in 
the ODMG. Is there any way to actually use proxied collections in the 
ODMG if ImplicitLocking is set true?

It seems to retrieve every collection (in fact it is worse as it 
retrieves size, then retrieves collections) by default as soon as the 
parent object is loaded unless ImplicitLocking is disabled. This is 
true even when optimistic locking is in use!

-Brian



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Re: Optimistic Transactions, Proxies, and Locking in ODMG

Posted by Brian McCallister <mc...@forthillcompany.com>.
Okay, the fix introduces a new interface: CollectionProxy

Right now the pluggable collection proxy system Jakob put in does not 
require this, and the CollectionproxyListener still accepts the 
CollectionproxyDefaultImpl on its callback methods. As soon as we get 
1.0 out the door I want to change this to talk to the interface. This 
will work fine for all of our internal stuff, but as I presume the 
pluggable CollectionProxy implementation was added for a reason, I 
don't want to break it for that person in 1.0.

-Brian

On Jun 9, 2004, at 10:08 PM, Brian McCallister wrote:

> Found the problem, will work on a fix. Hopefully can get it in 
> tomorrow.
>
> -Brian
>
> On Jun 9, 2004, at 7:19 PM, Brian McCallister wrote:
>
>> I am trying to figure out (and document!) proxy and locking behavior 
>> in the ODMG. Is there any way to actually use proxied collections in 
>> the ODMG if ImplicitLocking is set true?
>>
>> It seems to retrieve every collection (in fact it is worse as it 
>> retrieves size, then retrieves collections) by default as soon as the 
>> parent object is loaded unless ImplicitLocking is disabled. This is 
>> true even when optimistic locking is in use!
>>
>> -Brian
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Re: Optimistic Transactions, Proxies, and Locking in ODMG

Posted by Brian McCallister <mc...@forthillcompany.com>.
Found the problem, will work on a fix. Hopefully can get it in tomorrow.

-Brian

On Jun 9, 2004, at 7:19 PM, Brian McCallister wrote:

> I am trying to figure out (and document!) proxy and locking behavior 
> in the ODMG. Is there any way to actually use proxied collections in 
> the ODMG if ImplicitLocking is set true?
>
> It seems to retrieve every collection (in fact it is worse as it 
> retrieves size, then retrieves collections) by default as soon as the 
> parent object is loaded unless ImplicitLocking is disabled. This is 
> true even when optimistic locking is in use!
>
> -Brian
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org