RE: Use of DB2 constraints

[Buck Calabro <buck.calabro@xxxxxxxxxxxxxxxxx>]

I took the liberty of changing the subject line.

We used IrWin a while ago to remodel one of our applications.  It places
constraints on tables for you.  There's a learning curve for classic RPG
programmers.  When one tries to update a table and that attempt violates a
constraint, DB2 throws an I/O error.  There aren't many RPG programmers
accustomed to checking for I/O errors on EXCPT, WRITE, DELET and UPDAT...

Constraints are nice because programmers and auditors can't accidentally use
DFU or SQL to mung up your database.  They are not nice because restoring
and copying tables isn't as straightforward as without them.  All in all, I
would say they are a Good Thing to use; especially for new tables.

Buck Calabro
Commsoft; Albany, NY
"Nothing is so firmly believed as
 that which we least know" -- Michel Montaigne
Visit the Midrange archives at http://www.midrange.com

> -----Original Message-----
> From: Graap, Ken 
> Sent: Thursday, March 29, 2001 12:10 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: Triggers or Journals?
> 
> >IBM is going gung ho with triggers for editing on their files.
> 
> I wonder why there isn't a broader use of DB Referential Constraints in
> DB2/400? Moving editing logic into the database and out of application
> code
> sure seems to make sense. Is anyone moving their DB editing logic into
> DB2/400 via DB Constraints?
> 
> Kenneth
> 
> ****************************************
> Kenneth E. Graap
+---
| 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
+---