|
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of DeLong, Eric
Sent: Wednesday, January 09, 2008 5:10 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Checking for dupe key on WRITE
Brad,
The suggestion is not that you simply don't handle the
exception.... That would be stupid.... The suggestion is, for
cases where exceptions are infrequent, to handle the exceptions
via monitor (exception handler). In other cases, the pre-check
code might be more efficient.
Its a design choice.
Eric
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Bradley V. Stone
Sent: Wednesday, January 09, 2008 4:48 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Checking for dupe key on WRITE
And if there is, and you didn't check for it and/or monitor for
you, you're
spending lots of time answering phonecalls! :)
cpu cycles for a pre-check are the least of my wories.
-----Original Message-----mailing list
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of DeLong, Eric
Sent: Wednesday, January 09, 2008 4:46 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Checking for dupe key on WRITE
Only if there is an actual collision.... If no collision, then
the pre-check on every write would be 100% wasted time....
Eric
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of James Lampert
Sent: Wednesday, January 09, 2008 4:42 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Checking for dupe key on WRITE
Bradley V. Stone wrote:
In a worst case scenario, yes. But that doesn't mean youshould only use
the duplicate key error and NOT check for existance beforeblindly writing a
record.
Indeed. A key collision uses up significantly more system time and
resources than pre-checking.
--
James H. H. Lampert
Touchtone Corporation
--
This is the RPG programming on the AS400 / iSeries (RPG400-L)
To post a message email: RPG400-L@xxxxxxxxxxxxmailing list
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L)
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.