× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Brian Johnson
Sent: Wednesday, January 09, 2008 4:02 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Checking for dupe key on WRITE


On Jan 9, 2008 3:03 PM, Bradley V. Stone <bvstone@xxxxxxxxxxxx> wrote:

hopefully if you're writing to a file (or updating) you're
using your only
single unique access path (you do only have one, right? if not... ugh!)



Well, it really doesn't matter. As others pointed out, unless you have a
lock on the table the precludes any other updaters, there is no guarantee
that another process won't write the "new" key value between your test for
existence and your insert. So you really need to handle duplicate key
error.


In a worst case scenario, yes. But that doesn't mean you should only use
the duplicate key error and NOT check for existance before blindly writing a
record.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.