Re: Best Practices on DB2 SQL Databases

["Raul A. Jager W." <raul@xxxxxxxxxx>]

Updating a sub-set of the datbase is a SQL job, Relational Integrity can 
be done with DDS, using ADDPFCST after creating the "files" (or tables).
But, I like better the SQL way.

rob@xxxxxxxxx wrote:

> I think that everyone has their idea of "user friendly".  Is it user 
> friendly when they ask you to change all assets that are in Texas to have 
> a different tax rate in the fixed asset database to do a 
> update fadata set taxrate=.123 where state='TX'
> versus having them edit every record using the software?  My user thought 
> so.
>
> If you think that automatically stopping the user from deleting an order 
> number because it has order lines associated with it is user friendly then 
> you may want to trash using DDS to define your data and use DDL and 
> specify constraints.
>
> If you're looking for something that generates a multicolor prompt screen 
> with pictures and all sorts of other bells and whistles that's not the job 
> of SQL.  SQL just may be the method which the tool that provides the bells 
> and whistles uses to update the data.
>
>
> Rob Berendt
>