Re: Lock timeout on oracle 8i

On a slightly less extreme set of comments ... yes, buy Tom's book, as it explains the differences (and why!) between Oracle and other database vendors in how they handle locking and concurrency. You cannot just pick up and drop SQLserver code onto an Oracle database and expect it to work, as although the code
may look the same, Oracle implemented a 'different' way of managing locks/concurrency. Basically readers never block writers and writers never block readers.
Its neat, but it does cause confusion when people migrate from one to the other. Also read the "Oracle Concepts" book. If 2 people are trying to update the same row/column one of them will block (wait) until the first session either commits or rolls back. You will need to recode the logical of the application to achive the same results. Do you actually need to switch to Oracle?

Alun

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:berseu054i1hvr79spg27rkgpgh4gnvo2h_at_4ax.com...
> There is no such thing as a lock time out in Oracle, as you don't need
> it, because readers don't block writers.
> I STRONGLY URGE YOU TO TRY TO *LEARN* ORACLE AND TO RETURN FROM YOUR
> WAY TO HELL, because if you plan to develop ALL YOUR CODE IN THE
> FASHION YOU DID ABOVE, YOUR SYSTEM IS GOING TO BE *DISASTROUS*
>
> BUY Expert One on One Oracle by Thomas Kyte READ IT AND PUT IT UNDER
> YOUR CUSHION AT NIGHT
>
> STOP THINKING Oracle IS SQLSERVER SOLD BY A DIFFERENT VENDOR.
> FORGET EVERYTHING YOU LEARNED UNTIL NOW.
>
Received on Sun May 26 2002 - 06:27:14 CDT