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