Kerry Moorman
1/4/2008 1:42:00 PM
Jonathan,
Of course "last in wins" is a valid strategy for some applications. I am
always interested in understanding just how that strategy is actually used.
When a user retrieves a row from a database table and changes one or two
columns of data in that row, does your app track which columns have been
changed and only update those columns in that row in the table? Or does your
app, in the process of updating the row in the table, re-write the unchanged
columns to the table in addition to updating the changed columns?
Kerry Moorman
"Jonathan Wood" wrote:
> Kerry,
>
> > So you are saying that you generally handle concurrency with the "last in
> > wins" strategy?
>
> Why not? If someone wants to set a field to one value, and someone later
> wants to set it to another (even if only milliseconds later), why should I
> prevent the field from being changed just because it had been changed
> earlier?
>
> Jonathan
>
>