|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] I still say a simple service program should be able to format the messages for the users sake. You've got the original message number and the two files. Like the other fellow said, there are files like SYSCST. Then there is QADBIFLD to get field descriptions. What more would it take? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Walden H. Leverich" <WaldenL@TechSoftInc.com> Sent by: midrange-l-admin@midrange.com 04/24/2002 01:27 PM Please respond to midrange-l To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> cc: Fax to: Subject: RE: SQL help >From: Vernon Hamberg >I mean, some of the code would be leaner, but... I'm not sure I even agree with that. While the database would prevent you from violating the RI constraints you may still do code-level RI checking just so you can return more user friendly messages to your users. I don't see the code being all that less complex if we have to monitor for each possible RI violation in an update and then figure out what caused the violation and return an appropriate message to the user. I thing RI in code is still necessary, however I also put the RI in the database so I can be assured that something outside my code (DFU, SQL, JDBC, etc.) doesn't screw up my tables. -Walden _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.