Re: SQL issue with EXISTS not "working"

We are on V5R4. MERGE was available in V7.1.

On Thu, Oct 23, 2014 at 9:57 PM, Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:

So, given:

1) COMMON_FILE is empty when you start
2) ITEM values are unique in FILE_A

Then I think all the records in FILE_A should be inserted into
COMMON_FILE. Does this happen?

How are you proving "The exists is not working and as a result the insert
is inserting duplicates"? Are you sure you are doing this correctly?

You can check for duplicate ITEMS simply with something like this:
SELECT ITEM,COUNT(*)
FROM COMMON_FILE
GROUP BY ITEM
HAVING COUNT(*) > 1

Sam

On 10/23/2014 10:56 AM, Darryl Freinkel wrote:

I need some help on this one.

I am merging 5 company records into 1 file and need to drop any
duplicates.
This is the statement:
INSERT INTO COMMON_FILE
(SELECT * FROM FILE_A A1
WHERE NOT EXISTS (SELECT 1 FROM COMMON_FILE A2 WHERE A1.ITEM = A2.ITEM))

Problem:
The exists is not working and as a result the insert is inserting
duplicates.

What alternative ways are there to achieve this merge or what mistake am I
not seeing?

I have 5 similar SQL statements to run.

TIA

---
This email is free from viruses and malware because avast! Antivirus
protection is active.
http://www.avast.com


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.