-----Message d'origine-----
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Dennis Lovelady

I've just been asked to look into adding constraints to a
database (as
an alternative to triggers on the database, and exit
programs on the
application).

Let's start with information about the types of constraints.
What is the business need? There are some constraints you're
probably used to already (though they go by a different
name), such as UNIQUEness of a key. There can be constraints
that ensure that data is not orphaned (such as an order
record without a matching customer record) and so on. What
type are we talking about here?


And when you get round to actually implementing something, many of us will like to hear what you did, how and why, etc, etc.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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