Re: Pros and Cons of DB defined Referential Integrity Constraints -- MIDRANGE-L

Subject: Re: Pros and Cons of DB defined Referential Integrity Constraints
From: rob@xxxxxxxxx
Date: Mon, 22 Oct 2012 07:36:05 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

There have been numerous discussions on coding RPG's WRITE processing on
where the break even point is, performance wise, on prechecking versus
just doing it with %error on the write. Apparently it takes quite a few
before prechecking is worth it. But most people who do the %error do
remove the error from the joblog, IF, they've successfully handled it
within the program.

Rob Berendt

This mailing list archive is Copyright 1997-2026 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.