Subject | Re: Deadlock with select-storedprocedure |
---|---|
Author | josef_gschwendtner |
Post date | 2007-03-09T09:06:30Z |
--- In firebird-support@yahoogroups.com, Thomas Steinmaurer <ts@...>
wrote:
sets internally :
isc_tpb_write
isc_tpb_wait
isc_tpb_read_committed
isc_tpb_rec_version
Josef
wrote:
>* from
> Josef,
>
> > once in a while we get a deadlock executing the statement "Select
> > SP_SWAP_MD(Someparameters)".statement
> > SP_Swap_MD is a stored procedure which only contains a select-
> > joining 3 tables.335544336.
> >
> > Details:
> > - The exception is: java.sql.SQLException: GDS Exception.
> > deadlock(Jaybird)
> > - All transactions do have the isolation-level READ_COMMITTED
> >tables at
> > Although, there might be an update performed to one of these
> > the time this stored proc is executed, we kind of thought thereis no
> > deadlock with select-queries. Is this wrong?during a
> >
> > If it is wrong, under which circumstances a deadlock can occure
> > select-statement (read).procedure
>
> If you have started your transaction for the selectable stored
> with the NO_RECVERSION option, then it won't be able to read arecord
> which has been updated by a transaction yet uncommitted.We use Jaybirds "TRANSACTION_READ_COMMITTED" which (as far as we know)
>
> "Good" old MSSQL2000 style. ;-)
>
sets internally :
isc_tpb_write
isc_tpb_wait
isc_tpb_read_committed
isc_tpb_rec_version
Josef