What do you mean by "(ideally, specified by database, like the type
maps)"? Is this because some databases other than Oracle do table or
block locks when doing a "select for update"?
Bill
Dan Christopherson wrote:
> It would have to be optional behavior (ideally, specified by database,
> like the type maps), but I think it's a great idea.
>
> On Wed, 21 Mar 2001, Bill Burke wrote:
>
>> Hi all,
>>
>> (Where should I email questions like this? Jboss-Dev, Jboss-User,
>> JBoss-CMP? Thanks)
>>
>> Why not have the ability to "select for update" in CMP for an EntityBean
>> load? I know this is unnessary when only one instance of JBoss is
>> running or if the bean is marked as read-only, but what happens when you
>> have more than one JBoss hitting the DB? Since clustering is not
>> supported, is this a good way to manage multiple instances of JBoss
>> hitting the same datasource?
>>
>> You could make all your connections TRANSACTION_SERIALIZABLE, but
>> doesn't that create performance problems? Also, with serializing, it
>> kind of sucks that the whole transaction is rolled back if one row in
>> one table has serialization issues.
>>
>> Also, maybe "select for update" can be used as an optimization for the
>> LOCKING-WAITING performance problem discussed earlier by Marc and Simone.
>>
>> Regards,
>> Bill
>>
>>
>> --
>> This is the JBossCMP mailing list. Please send email to '[EMAIL PROTECTED]'
>> with the command 'unsubscribe jbosscmp [email@address]' in the body of the mail
>> to be removed from this list.
>>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
