×
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.
IMO, RI constraints are a safety net, and your app should try and interdict those violations before they make it to the DB.
-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Wednesday, May 17, 2017 9:26 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Some database discussions...
How did the parent know to chain out to the child on which column to
ensure that there was no match and therefore it would be safe to
remove this parent row?
My problem with DB defined RI constraints is with the generic non-descriptive error messages, and that the error handling doesn't provide for cursor positioning and highlighting on relevant columns.
I may be missing something. For shops that implement DB defined RI constraints, how do they handle user interface requirements (i.e. friendly, meaningful error messages, cursor positioning on relevant columns, and highlighting)?
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.
midrange.com
