×
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.
Then your sub-SELECT is not coded correctly.
One way to ensure it doesn't insert existing IDs would be to turn the
sub-SELECT into an EXCEPTION JOIN on QTEMP/FOO table, i.e.:
"INSERT INTO QTEMP/FOO (FLD1) SELECT DISTINCT . . . . EXCEPTION JOIN
QTEMP/FOO USING(commonIdField)"
I'm sure there are other ways to insure uniqueness, probably more fitting
depending on your situation.
Elvis
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com
-----Original Message-----
Subject: Re: SQL0803: "duplicate key value specified"
Dunno where I left my brain this morning.
The complete statement IS an insert, in the form "INSERT INTO QTEMP/FOO
(FLD1) SELECT DISTINCT . . . ."
--
JHHL
This mailing list archive is Copyright 1997-2025 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.
midrange.com
