RE: SQL delete not in related table

Good catch Elvis, you are correct.

Note to Jeff.  The RDBMS way to do this is to have primary/foreign keys defined 
with cascading deletes.

When you delete the records from the header file, the DB would automatically 
delete the records from the detail file.

HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Elvis Budimlic
> Sent: Friday, June 17, 2005 10:23 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: SQL delete not in related table
> 
> 
> I think Jeff wanted NOT EXIST...
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
> Sent: Friday, June 17, 2005 9:16 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: SQL delete not in related table
> 
> Jeff,
> 
> As you can see, what's wrong is it doesn't work ;-)
> 
> In other words, it's not valid syntax.
> 
> Try this:
> 
> delete 
> from podtl A
> where exist ( select 1 
>               from pohdr B
>               where A.vndnr = B.vndnr
>                 and A.weekx = B.weekx
>                 and A.digit = B.digit
>             )
> 
> 
> HTH,
> 
> 
> Charles Wilt
> --
> iSeries Systems Administrator / Developer
> Mitsubishi Electric Automotive America
> ph: 513-573-4343
> fax: 513-398-1121
>  
> 
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Jeff Crosby
> > Sent: Friday, June 17, 2005 10:02 AM
> > To: 'Midrange Systems Technical Discussion'
> > Subject: SQL delete not in related table
> > 
> > 
> > OK, I've spent about an hour trying to figure this out.  SQL 
> > does not like
> > the following statement:
> > 
> > DELETE FROM PODTL WHERE (VNDNR, WEEKX, DIGIT) NOT IN               
> >                         (SELECT (VNDNR, WEEKX, DIGIT) FROM POHDR);
> > 
> > I did this identical thing a half dozen times yesterday 
> > *EXCEPT* there was
> > only one field name to match on, not 3.  I've looked at 
> > manuals and googled.
> > I've tried with/without parens, with/without commas to no 
> > avail.  All the
> > examples I find do it on only one field.
> > 
> > What's wrong with the syntax?
> > 
> > -- 
> > Jeff Crosby
> > Dilgard Frozen Foods, Inc.
> > P.O. Box 13369
> > Ft. Wayne, IN 46868-3369
> > 260-422-7531
> > 
> > The opinions expressed are my own and not necessarily the 
> > opinion of my
> > company.  Unless I say so.
> > 
> > 
> > 
> > -- 
> > 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.
> > 
> > 
> 
> -- 
> 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.
> 
> 
> 
> 
> -- 
> 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.
> 
>