Re: SQL help

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
But you are using traditional logic.  Traditional logic says to verify
each field yourself.  For example if you are entering an item number with
an item class then verify that the item class exists.  However, 'thinking
outside the box' says that if you have the RI constraints in place you can
just write the item record and interpret any messages you get.  After all,
why duplicate the logic that is already in place for your RI and/or
triggers?  Sooner or later some clod will update the data from outside the
one 5250 program you think is the only method to update the file.  A
program this way should be more efficient.  You wouldn't have to read all
the upper level files yourself.  Your program logic would be much simpler.
 And it will be easier to convert from one method of presentation to
another.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Richard B Baird" <rbaird@esourceconsulting.com>
Sent by: midrange-l-admin@midrange.com
04/24/2002 11:26 AM
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Fax to:
        Subject:        Re: SQL help



In regards to what errors you would give for constraint violations,
personally, I would simply allow the hard crash.  The application should
be
written in such a way that constraint violations would never happen,
unless
someone tried to DBU, DFU, SQL insert/update an on-the-fly fix or other
non-standard method.

Any application constraint errors should come out in testing, and if one
slips by into production, then I'd want a hard crash to call my attention
to the problem.

of course this assumes you've got recovery procedures in place.

Rick
---original messages----
Good morning, gentlemen.
May I ask you which text do you use for customer who enter record that
violates constraints ?
Are you able to send them meaningful messages ?
Sincerely
Domenico Finucci


Good question.  What message do you currently send when a write to a file
fails?  Or is the common practice of ignoring the indicator, or whatever,
on a write employed.

Rob Berendt

_______________________________________________
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.