RE: Use of DB2 constraints

["Graap, Ken" <keg@xxxxxxxxxxxxxxxxxx>]

>The problem with constraints is that they are very unforgiving
> of programmer errors and programmers...

But, in a world where update access to data may no longer be exclusively
controlled through RPG application code, some kind of change will eventually
have to happen. Especially if we want to insure the data integrity of our
shared databases.

I know change is difficult but, system programmers may need to adjust to a
new way of doing things. These changes could eventually make things more
solid and less error prone too. Removing editing logic from the application
and applying it directly to the database would result in simpler application
code. It would also insure that changes made to data from any source use the
same rules. 

Changing how we do things may just be the price we have to pay as we
integrate our corporate databases into cross system applications that are
all connected over networks.
 

Kenneth
 
-----Original Message-----
From: NSmith@lincare.com [mailto:NSmith@lincare.com]
Sent: Thursday, March 29, 2001 10:34 AM
To: MIDRANGE-L@midrange.com
Subject: RE: Use of DB2 constraints


The problem with constraints is that they are very unforgiving of programmer
errors and programmers seem to take umbrage at that.  Just try convincing an
old line RPG programmer that he oughta write the header BEFORE he writes the
detail and you'll see what I mean......

+---
| 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
+---