Skip site navigation (1) Skip section navigation (2)

Re: BUG: PGACCESS does not warn when trying to update a

From: Jean-Luc Lachance <jllachan(at)nsd(dot)ca>
To: terry <tg5027(at)citlink(dot)net>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: BUG: PGACCESS does not warn when trying to update a
Date: 2002-08-15 16:12:20
Message-ID: 3D5BD2E4.A7F1F769@nsd.ca (view raw or flat)
Thread:
Lists: 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

In response to

Responses

pgsql-interfaces by date

Next:From: Bruce MomjianDate: 2002-08-16 04:58:24
Subject: Re: libpgtcl modifications
Previous:From: Hal DavisonDate: 2002-08-15 16:10:29
Subject: Re: BUG: PGACCESS does not warn when trying to update

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group