× 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.


  • Subject: Re: SQL vs DDS
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Thu, 26 Aug 1999 8:26:54 -0500

Joe,

You have a good point there.  SQL is imbedded into the operating system.  What 
you are 
paying for is:
The SQL precompiler
The SQL prompter (STRSQL)
The prompter for Query Management (STRQM).
The SQL statement runner (RUNSQLSTM).

Frankly the SQL precompiler runs so far behind the languages that it is a 
robbery of our 
money to pay support for that.  No nested /COPY statements, etc.

The SQL prompter is a blessing and a curse.  It is a blessing in that it makes 
it easy to 
construct SQL statements.  It is a curse in that if you don't study the manuals 
you will 
not learn of many of the other functions you can get out of SQL with more 
complex statements.  
It also has grounds for improvement:  prompting for LIKE fields from the 
database catalog 
when doing the CREATE TABLE.

Query Management is cool.  You can develop the Query on the development 400 and 
run it on 
any 400, (STRQMQRY).  You don't have to hardcode your library names like 
Query/400.  In 
fact IBM would like to obsolete Query/400 and replace it with Query Management. 
 Perhaps 
this is what you should do.  On all new production machines buy SQL instead of 
Query.  
IBM has figured out how to handle one of the limitations of Query Management:  
Query will 
merge with OV/400, Query Management won't.  Thus IBM killed OV/400.

RUNSQLSTM is nice, but you can accomplish the same with STRQMQRY.





There are far too many companies that will not provide anything beyond
what is included in ADTS. It's why tools like Code/400, CodeStudio and
FlexEdit are only marginally used. A cross-reference tool like Hawkeye is
fairly common and some sort of change management is becoming a little
more common place. Why isn't the SQL product part of the ADTS? Raise
the price of ADTS and include it. SQL will never become part of the 
"common" RPGers toolset until this happens.

Joe Teff
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.