On 19/03/2010 11:35 PM, Little, Douglas wrote:
> The update can’t then locate the row (timestamp mismatch), and displays
> the ‘write conflict’ error.
Change the ODBC driver settings to issue updates by primary key, and the
issue goes away. IIRC it's done in some backward-ish way like turning
off "row versioning".
--
Craig Ringer