Uh-oh. Here comes the flood.
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx / John Wallroff
> Sent: Wednesday, October 06, 2004 12:20 PM
>
> OMG, that whole "Assume" analogy is so 70's.
>
> I think the biggest problem is with programmers that think their database
> design takes the place of good coding. Referential constraints
> are meant to
> be a last line of defense in database maintenance. They don't take the
> place of good program code.
>
> -----Original Message-----
> From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
> Sent: Wednesday, October 06, 2004 10:56 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: Write statement
>
> Is that the ONLY condition that will cause it? I don't think so.
> What other conditions may cause such an error?
> - File full
> - Duplicate key
> - error on the trigger program associated with the file
> - referential constraint error.
>
> I think the biggest problem we have in getting developers to start using
> triggers, constraints and basically coming out of the 70's with their
> database design is a fear that they will have to bring their
> coding out of
> the 70's also.
>
> Goes back to the basic lesson: Assume can be broken down into
> three words
> A$$/u/me, or, you make an a$$ out of u and me when you assume.
>
> Rob Berendt

This mailing list archive is Copyright 1997-2015 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 here. If you have questions about this, please contact