Then you're not COMMITting your transaction.


With regards,

Martijn Tonies

Firebird Workbench - the developer tool for Firebird
http://www.upscene.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."

> Okay another funny if I run the same update 2 quickly after each other

from

> the same machine (DB Explorer)
> then it hangs on the second one ...
> Why ?>?
>
>
> Thanks
>
>
> At 15:42 28/11/2002 +0200, you wrote:
> >After I added the WAIT ON LOCKS entry the SQL Passthru is SHARED

NOAUTOCOMMIT

> >and theSQLQRYMODE Is SERVER and the COMMIt RETAIN is TRUE
> >then we get all kind of funnies as they get deadlocks and this is a
> >specific column
> >
> >When I create a index for it is is fine for a while and then starts

giving

> >deadlocks again..
> >
> >what can this be ???
> >I dont know where to go to anymore :(
> >
> >
> >Johannes
> >
> >
> >At 15:26 28/11/2002 +0200, you wrote:
> > >Well how about the 4096 with the setting COMMIT RETAIN will that work
> > >as we have the following problem
> > >
> > >When they update record it hangs every now and again
> > >there is about 10 people working. Also the deadlocks are becoming more

and

> > >more.
> > >
> > >In the interbase log file I have a LOT of 10054 Socket Errors Server

side

> > >that says the host went down.
> > >
> > >Can this endup in a dead lock for the others ??
> > >
> > >Thanks in Advance
> > >Johannes
> > >
> > >
> > >At 10:52 28/11/2002 -0300, you wrote:
> > > >In the jurassic period, when I used BDE, I think my settings was flag
> > > >= 4608. It worked OK, considering the obvious BDE limitations.