> -----Original Message----- > From: Tom Lane [mailto:[EMAIL PROTECTED]] > > Hiroshi Inoue <[EMAIL PROTECTED]> writes: > > Your settings probably worked well under 7.1 but > > doesn't in 7.2 due to the following change in > > tcop/postgres.c. > > AFAIR, there is only a visible change of behavior for > INSERT/UPDATE/DELETE queries, not for SELECTs. So I don't think > this change explains Ron's complaint.
For a view a_view UPDATE a_view set ... where xxxxx; returns UPDATE 0 in any case in 7.2. The psqlodbc driver understands that no row was updated and returns the info to the upper application if requested. MS access( and I) think there's no such case other than the row was changed or deleted after it was SELECTed. Note that MS access doesn't issue any SELECT commands to check the optimistic concurrency of the row. The where clause of the UPDATE command contains *a_item = old_value* for all items to check the optimisitic concurrency at the same time. regards, Hiroshi Inoue ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
