why??? you have to use that timestamp technique in SQLServer, because they
don't have row level locking, oracle only locks it when you're changing the
row.
AND unlike others writers don't block readers and readers don't block
writers.
you also don't have to worry about the dirty read problem either.
Let the db handle it for you....
Thor HW
Brian K. Lawton wrote in message <6gnqgc$86d$1_at_ha2.rdc1.md.home.com>...
>If I'm trying to implement optimistic concurrency within my database, is
the
>RowId attribute the correct place to be checking? If not, what is Oracle's
>equivalent to SQL Server's timestamp datatype?
>
>________________________________________________
>Brian K. Lawton (mailto:Lawton_at_RDAConsultants.com)
>RDA Consultants Limited (http://www.RDAConsultants.com)
>
>
>
Received on Sat Apr 11 1998 - 00:00:00 CDT
