Please give some examples where you would need the dbms to do the
referential integrity?
Ken
----- Original Message -----
From: "pak" <[EMAIL PROTECTED]>
To: "Ken Sommers" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, July 10, 2001 8:31 PM
Subject: Re: Referential Integrity
> So is MySQL not suitable for large corporate database ?
> ----- Original Message -----
> From: "Ken Sommers" <[EMAIL PROTECTED]>
> To: "pak" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, July 11, 2001 1:24 PM
> Subject: Re: Referential Integrity
>
>
> | hello,
> | Do simple input validation.
> |
> | If the user is entering what is supposed to be a primary key value,
> | make sure it is a valid key before sticking it in any where, If it's a
> bogus
> | key .tell the user to try again.
> |
> | If user wants you to delete rows from a primary table (customer)that
have
> | "foreign keys"( cust ID in Orders)that are still pointing to
> | something.(related table)..tell the user that this customer still has
> | orders( yes you'll have to check yourself),,and deleting all those
orders
> | would make the accountants and IRS really mad. and you can;t delete the
> | customer without deleting all the orders,,and tell them further more
> ,,that
> | deleting primary keys is bad practice anyway..should just set the active
> | flag to "NO"..cuz you still want all the history involved with that
> customer
> | around.. and further more,..IF a few years down the line that customer
has
> | been inactive for a buncha years kill him or her then. and all the
related
> | orders .but only after the history files have been summarized and tucked
> | away.
> |
> | User wants to change a primary key value,,just don't do it..:) too much
> | work..OR tell 'em it will cost 'em.
> |
> | have fun,
> | Ken
> |
> |
> |
> | ----- Original Message -----
> | From: "pak" <[EMAIL PROTECTED]>
> | To: <[EMAIL PROTECTED]>
> | Sent: Tuesday, July 10, 2001 7:17 PM
> | Subject: Referential Integrity
> |
> |
> | > MySQL does not support RI, anyone has good suggestion that do this in
> the
> | > program ?
> | > As this would be a nightmare if I have 50 detail tables to update
> | > programmatically.
> | >
> | >
> | > ---------------------------------------------------------------------
> | > 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
> | >
>
>
---------------------------------------------------------------------
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
