while i don't mind constraints, etc...if the checking and validation ISN'T
done in the application, you'll have stuff crapping out and never making
it into the database and troubleshooting is a PITB...so moral of my lil
story, force your programmers to do the checking first and ensure they are
following the process or you'll be sorry...
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
03/10/2008 10:00 AM
Re: Which of the SYSIBM tables/views show the row count for
Why does it drive you bonkers to put any constraints and triggers on the
database? Why do you insist it be ONLY in the application (or some
In that case, why use externally defined files? After all, you can put
all the column descriptions in your applications. People did this for
years on the S/34 and S/36. And punched cards before that. If you are
truly using only application programming to access the database, or
wrappers, why would you need the external definitions? I've worked with
vendor applications in which the column, and table, text were pretty much
limited to "Copyright".
And it would be glorious if applications never had an error,
If no one ever hacked into data for malicious purposes,
And if no one ever made a keying error when using a database utility
And if no one ever had a need, or use, for UPDDTA, WRKDBF, or such
But everyone joining hands and singing "Kumbaya" is not going to make it
Therefore journalling, constraints and other tools should be used.
This thread ...
Re: Which of the SYSIBM tables/views show the row count for, (continued)
This mailing list archive is Copyright 1997-2019 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