Re: SQL vs DDS

John P Carr wrote:
> 
> In addition to using a new tool,   we should also rethink our process.
> The use of most of the new funcitions in SQL (Constraints, etc)  will
> require us to rethink HOW we Design our applications.    In the case
> of Constraints for example,  Your programs better be ready for
> error messages on Updates/Writes/Deletes.   Also you have to
> remove all those edit checks in your applications and move them
> to the Data Base.  (Right Bruce?)
> 

Yes on the rethink. Problem is that the edit checks that were in the
database should have been enforced at the database level and not just
the display level. Water under the bridge, over the dam and out to the
sea...

As for the errors on the IO statements, being a COBOL programmer,
checking the status codes after the IO comes naturally. I do admit that
in many of my early RPG programs, that error check was lacking and
suspect that most of the existing RPG does not have the error checking
in it.

HOWEVER... if you are going to use SQL, then embed it. This more or less
forces you to check the SQLSTATE and SQLERROR returns. My personal
preference is for the SQLSTATE as it is much more consistent across
platforms. The only value that seems to be common to the SQLERROR is the
100 return for record not found.

-- 
===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified AS/400 Professional System Administrator
 -- IBM Certified AS/400 Professional Network Administrator

"The sum of all human knowledge is a fixed constant.
    It's the population that keeps growing!"
+---
| 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
+---