From: Jean-Luc Lachance <jllachan@nsd.ca>
To: terry <tg5027@citlink.net>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: BUG: PGACCESS does not warn when trying to update a
Date: Thu, 15 Aug 2002 12:12:20 -0400
Message-ID: <3D5BD2E4.A7F1F769@nsd.ca> (raw)
References: <20020405083629.6a97dcde.dbr@informactis.com>
<24205.1018020022@sss.pgh.pa.us>
<3D5AD9BF.F127D21A@nsd.ca>
<200208142339.TAA10893@beamish.nsd.ca>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: jllachan@nsd.ca, tg5027@citlink.net
Subject: Re: BUG: PGACCESS does not warn when trying to update a
In-Reply-To: <3D5BD2E4.A7F1F769@nsd.ca>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox