Re: implement a referential integrity constraint (long)

On May 8, 11:01 pm, Philipp Post <Post.Phil..._at_googlemail.com> wrote:
> > Can anyone suggest a better way? <
>
> 1) Do a web search about "Normal Forms" and get a book about database
> design
> 2) Look up standards. Postal codes have standards. There are ISO
> country and location codes. A database can enforce them by DRI and
> CHECK constraints.
> 3) Do not confuse the front end (reporting / presentation layer) with
> the backend (database). How you print addresses on paper, based on
> local needs is a matter of the reporting tools and not the database.
>
> Sorry, but there are fundamental problems with your design.
>
> brgds
>
> Philipp Post

Damn right! We all know the design is imperfect, Philipp. Unfortunately the large, old system cannot be re-written (specifically, someone tried before and we know it will cost more than AU$50M (1997?) to do that, and a larger budget is not available). I am not in Utopia, where if you don't like your program/data structure you can simply throw it away an do it again. As I've said, I wouldn't do it that way; it's not my design, or my system.

Love it or hate it, the information is stored in that structure. My question is, GIVEN the existing structure, what is the best way to put some referential integrity in? Walking away is not an option, so I want to make the best job of it instead. Received on Tue May 12 2009 - 05:35:08 CEST