|
I agrre, partialy, ADDPFCST TYPE(*CHKCST) is the best option for values that are unlike to change, or to expand, like Y/N Male/Female, day of week, month. If your values are likely to change, a TABLE is a better option is ADDPFCST TYPE(*REFCST), it will allow only the values in your table. Besides, your table may contain aditional info, like the two letter initial for the states, an the complete name, etc., and SQL reading a joint will be very fast, because is seems that the optimizer uses the constraint. In some cases the restriction is even more complex, and in those cases you should use a trigger program. Good luck, Raul __________________________________________________________________________________________ El Thursday 14 October 2004 11:19, Holden Tommy escribió: > best solution is to add a check constraint. ADDPFCST TYPE(*CHKCST)or via > SQL using the ALTER TABLE statement. > > Thanks, > Tommy Holden
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
