| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | "Little, Douglas" <DOUGLAS(dot)LITTLE(at)orbitz(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] MS Access 2007 update write conflict problem & resolution |
| Date: | 2010-03-20 04:02:10 |
| Message-ID: | 4BA448C2.1000503@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2010-03-21 07:20:54 | Re: Bug: recent files reset |
| Previous Message | Josh Berkus | 2010-03-19 21:08:30 | Re: Request: get rid of annoyance with new SQL window |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-03-20 05:06:54 | Re: returns 0 row from plpgsql function |
| Previous Message | zhong ming wu | 2010-03-20 00:02:07 | returns 0 row from plpgsql function |