Re: BUG: PGACCESS does not warn when trying to update a - Mailing list pgsql-interfaces

From Jean-Luc Lachance
Subject Re: BUG: PGACCESS does not warn when trying to update a
Date
Msg-id 3D5BD2E4.A7F1F769@nsd.ca
Whole thread Raw
In response to pgaccess and libtcl  (Didier Bretin <dbr@informactis.com>)
Responses Re: BUG: PGACCESS does not warn when trying to update  (Hal Davison <hal@faams.net>)
Re: BUG: PGACCESS does not warn when trying to update  (Brett Schwarz <brett_schwarz@yahoo.com>)
List pgsql-interfaces
But,

When a record is updated with PgAccess, the least that it should do is
check the return status of the update to find that the record no longer
exists and warn the user!!!

JLL

terry wrote:
> 
> Actually, M$ Access does the same thing.  When a form (or query)
> is populated with the contents of a record, it no longer is
> changed within the database - only within the form (or query).
> It is only when the record is saved that there is any indication
> of change or deletion.  The only way to determine if the record
> in the form (or query) has been changed or deleted is to check
> that record in the database during the operation, which is not
> routinely done.
> 
> >>  DARN!!!
> >>
> >>  I have just wasted half a day updating record with PcAccess.
> >>
> >>  If one is updating a record that was deleted by someone else,
> >> PgAccess does not warn that the record no longer exists and
> >> silently accept the update.
> >>
> >>  Then, if the list is refreshed, the record is gone!!!
> >>
> >>  ---------------------------(end of
> >> broadcast)--------------------------- TIP 5: Have you checked
> >> our extensive FAQ?
> >>
> >>  http://www.postgresql.org/users-lounge/docs/faq.html
> 
> --
> 
> terry


pgsql-interfaces by date:

Previous
From: terry
Date:
Subject: Re: BUG: PGACCESS does not warn when trying to update a record that was deleted by someone else.
Next
From: Hal Davison
Date:
Subject: Re: BUG: PGACCESS does not warn when trying to update