But if they're in the same transaction, they must use the same isolation
level - per our discussion on the database doing an implicite commit
when you try to change levels. I don't think it makes logical sense to
talk about having two different transaction isolation levels in the same
transaction, either - either the transaction is serializable or the
transaction is read-committed.
-danch
Bill Burke wrote:
> I disagree....well, at least for our app, we have transactions where some
> entities really need to be serialized and other entities within the
> transaction are just fine with read_committed.
>
> Bill
>
>
>>-----Original Message-----
>>From: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED]]On Behalf Of David
>>Jencks
>>Sent: Tuesday, June 26, 2001 4:43 PM
>>To: [EMAIL PROTECTED]
>>Subject: Re: [JBoss-dev] High load...
>>
>>
>>Hi,
>>
>>Forgive me if I am talking nonsense, but doesn't it only make
>>sense to have
>>transaction isolation per transaction???? I very much doubt you will find
>>a db that can support several transaction isolation levels within one
>>transaction. I can't quite figure out what it would mean, either. So I
>>say, put it with the transaction requirements for methods - Requires,
>>Requires New, etc. Then you can set the isolation each time you start a
>>new transaction, based on this specification.
>>
>>david jencks
>>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
