"Daniel Morgan" <damorgan_at_x.washington.edu> wrote in message
news:1080689533.255946_at_yasure...
> > You can look at it from another angle:
> > If I need to look at a row and it is currently being updated. How do I
> > gamble? If I presume the update will commit then looking at old data
> > will result in a decision being made on stale data. That can be bad.
>
> Depends on whether the architecture is such that you have minimized the
> possibility of multiple transactions attempting to update the same row
> at essentially the same time. We all design to maximize our strengths
> and to minimize our weaknesses: Or at least we should.
Not if we are running a commercial erp product :(
--
Niall Litchfield
Oracle DBA
Audit Commission UK
Received on Wed Mar 31 2004 - 03:09:30 CST
