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

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Pros and Cons of DB defined Referential Integrity Constraints
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Thu, 18 Oct 2012 14:37:22 -0700 (PDT)
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>

Charles Wilt
http://search400.techtarget.com/tip/Name-that-constraint

That looks interesting. If I understand correctly, you give each constraint a name that either is a key, or includes a key to a message file, then write a common procedure to fetch the message based on it. The loop to read the program message queue seems a little messy. Is it reliable?

-Nathan

As an Amazon Associate we earn from qualifying purchases.

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