Subject | Re: [Firebird-Java] Re: Transaction and concurrent updates |
---|---|
Author | Miroslav Novak |
Post date | 2004-04-07T00:10:19Z |
The second transaction reports a deadlock, as ISQL does, if I set the
transaction parameters to empty array. What are the default transaction
parameters?
int[] trnPars = {};
conn1.setTransactionParameters(Connection.TRANSACTION_READ_COMMITTED, trnPars);
conn2.setTransactionParameters(Connection.TRANSACTION_READ_COMMITTED, trnPars);
Mirek.
transaction parameters to empty array. What are the default transaction
parameters?
int[] trnPars = {};
conn1.setTransactionParameters(Connection.TRANSACTION_READ_COMMITTED, trnPars);
conn2.setTransactionParameters(Connection.TRANSACTION_READ_COMMITTED, trnPars);
Mirek.
On Mon, 22 Mar 2004, Roman Rokytskyy wrote:
> > I appologize asking the same thing again and again, but I would
> > like to make sure that I understand database transactions well.
> >
> > I hope I am doing exactly the same operations in isql as in Java,
> > but results are different. Why?
> >
> > In the Java example if two transaction performs separately, the
> > result is different than if they run in parallel. As I know the
> > transaction should avoid such differences.
>
> Seems that I was wrong - second trancation should fail... I will
> check if that's a bug in JayBird or not. Interesting is that JayBird
> 1.0.x works the same. Either there's something I do not understand
> with transactions in Firebird too, or its a bug somewhere.
>
> I will check this more.
>
> Roman
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>