pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG: PGACCESS does not warn when trying to update a record that was deleted by someone else.
5+ messages / 4 participants
[nested] [flat]
* BUG: PGACCESS does not warn when trying to update a record that was deleted by someone else.
@ 2002-08-14 22:29 Jean-Luc Lachance <jllachan@nsd.ca>
0 siblings, 2 replies; 5+ messages in thread
From: Jean-Luc Lachance @ 2002-08-14 22:29 UTC (permalink / raw)
To: ; +Cc: pgsql-interfaces
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!!!
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG: PGACCESS does not warn when trying to update a record that was deleted by someone else.
@ 2002-08-15 00:07 terry <tg5027@citlink.net>
parent: Jean-Luc Lachance <jllachan@nsd.ca>
1 sibling, 0 replies; 5+ messages in thread
From: terry @ 2002-08-15 00:07 UTC (permalink / raw)
To: Jean-Luc Lachance <jllachan@nsd.ca>; pgsql-interfaces
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG: PGACCESS does not warn when trying to update
@ 2002-08-15 15:29 Brett Schwarz <brett_schwarz@yahoo.com>
parent: Jean-Luc Lachance <jllachan@nsd.ca>
1 sibling, 0 replies; 5+ messages in thread
From: Brett Schwarz @ 2002-08-15 15:29 UTC (permalink / raw)
To: Jean-Luc Lachance <jllachan@nsd.ca>; +Cc: pgsql-interfaces
You are correct. Looking at the code a bit, it looks like it does the
Right Thing when inserting a new record, but does not do the same for
updating a record.
Can you file a bug so that this can get tracked properly?
http://bugzilla.pgaccess.org
thanks,
--brett
On Thu, 2002-08-15 at 09:12, Jean-Luc Lachance wrote:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
--
Brett Schwarz
brett_schwarz AT yahoo.com
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG: PGACCESS does not warn when trying to update
@ 2002-08-15 16:10 Hal Davison <hal@faams.net>
parent: Jean-Luc Lachance <jllachan@nsd.ca>
1 sibling, 0 replies; 5+ messages in thread
From: Hal Davison @ 2002-08-15 16:10 UTC (permalink / raw)
To: Jean-Luc Lachance <jllachan@nsd.ca>; +Cc: terry <tg5027@citlink.net>; pgsql-interfaces
Well in my applications, we routinly check the availabiliy of the record
priod to an update operation as a matter of course.
We come from the old days of CISAM...<GRIN>
--Hal.
On Thu, 15 Aug 2002, Jean-Luc Lachance wrote:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG: PGACCESS does not warn when trying to update a
@ 2002-08-15 16:12 Jean-Luc Lachance <jllachan@nsd.ca>
parent: Jean-Luc Lachance <jllachan@nsd.ca>
1 sibling, 2 replies; 5+ messages in thread
From: Jean-Luc Lachance @ 2002-08-15 16:12 UTC (permalink / raw)
To: terry <tg5027@citlink.net>; +Cc: 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
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2002-08-15 16:12 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-08-14 22:29 BUG: PGACCESS does not warn when trying to update a record that was deleted by someone else. Jean-Luc Lachance <jllachan@nsd.ca>
2002-08-15 00:07 ` terry <tg5027@citlink.net>
2002-08-15 16:12 ` Re: BUG: PGACCESS does not warn when trying to update a Jean-Luc Lachance <jllachan@nsd.ca>
2002-08-15 15:29 ` Re: BUG: PGACCESS does not warn when trying to update Brett Schwarz <brett_schwarz@yahoo.com>
2002-08-15 16:10 ` Re: BUG: PGACCESS does not warn when trying to update Hal Davison <hal@faams.net>
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