• Subject: Re: SQL Existence Check
  • From: "Walden Leverich" <walden@xxxxxxxxxxxxxxx>
  • Date: Tue, 18 Nov 1997 18:52:03 -0500

First: Unacceptable! :-) I will find a way.

Second: We are writing a program to perform an action over a vendor supplied
file. I do not want the program to level check whenever the vendor adds a
new field to the end of the file. I agree that "classic" i/o would be better
here, but I figured I would give the list a chance to find a way. Generally
I use SQL where SQL makes sense (Set operations) and do the rest in RPG.

-----Original Message-----
From: John Carr <74711.77@compuserve.com>
To: Midrange-L <MIDRANGE-L@midrange.com>
Date: Tuesday, November 18, 1997 6:42 AM
Subject: SQL Existence Check

>RE: SQL Existence Check
>First,  No.
>Second, Why?
>If one wanted to screw in a screw, one wouldn't use a hammer.
>If I were going to update the AMT field of all records for DEPT 10
>I surely would UPDATE FILE SET AMT=500 WHERE DEPT = 10
>So why don't you want to use the best tool? Just curious?
> KEY     SETLL FILE              50
> IF    (*IN50 = *ON)
>Simplest to code
>Simplest to understand
>Most efficient usage of the RDBMS
>Again,  Just curious?
>I think (like a single record random retrieval) SQL's implementation
>compared to the native implementation is complex, contrived and
>inefficient.  And those are the good points.  BTW, I use both interactive
>& embedded SQL every day for SET at a time processing.

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

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

This mailing list archive is Copyright 1997-2019 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].