Well, dunno about that, but I've got a system here which I designed round
the fact that MySQL *doesn't* have RI.
When a customer gets deleted (or changes it's reference id), the data for
the old id has to remain in the system. I know that if I was using a
product which enforces RI I'd design it differently (i.e. keep the user
data and have an active/inactive flag), but what I've got here works -
at least for some values of "works".
Paul Wilson
iiNet Ltd
> Interesing,
> so when they need to delete a customer from the system,,they just turn the
> RI back on,,maybe at night when the 'regular' people have gone home?
>
> how do they do it?
>
> Ken
> >
> > In my experience, most "large corporate" databases
> > are not implemented with RI enabled. The RI constraints
> > often interfere with user workflows (incomplete data or
> > data entered out of sequence) and adds processing overhead
> > that adds up to serious cycle drain for lengthy runs.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
