* This is the modus mailing list *
Cascading Integrity is the only thing holding you back, and if the
latest version does include this ability it shouldn't be a problem. I
think the main reason is that Vircom only issues a delete from one off
the tables and expects the records to be removed from both.
Also, someone on this list wrote some triggers for MS SQL 7.0 to
accomplish the same thing and this might be possible with MySQL (I'm not
sure if MySQL supports Triggers).
---
Semper Ubi Sub Ubi. - Always wear Underwear.
(--------------------------------) {((((((
( Suneel Jhangiani ) /_ _ )
( Technical Director ) ( . . )
( Inter-Computer Technology Ltd. ) ( / )
(----------------------------------oOOo------------oOOo----)
( 40 James Street Tel: +44 (0) 20 7486 9601 )
( London W1U 1EU Fax: +44 (0) 7050 678 978 )
( United Kingdom Email: [EMAIL PROTECTED] )
( Website: http://www.inctech.com )
(----------------------------------------------------------)
-----Original Message-----
From: Lewis Watson [mailto:[EMAIL PROTECTED]
Sent: 10 November 2003 06:42
To: [EMAIL PROTECTED]
* This is the modus mailing list *
Also, MySQL 4.0.16 (latest production release) has foreign key
capability
which allows cascading deletes. So is there anything else? If not then
perhaps there will not be any other potential problems.
Thanks,
Lewis
----- Original Message -----
From: "Lewis Watson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 10, 2003 12:20 AM
Subject: [Modus] The Quarantine and MySQL Revisited
> * This is the modus mailing list *
>
> I have a question regarding the Quarantine and MySQL. Can someone
(Suneel?
> :-) please explain what functionality is needed that may keep MySQL
from
> being used. Also, I remember one of the issues being cascading
deletions
> ( cascading referential integrity constraints ). Is this the only
> potential problem that is known or are there others as well? I am
about
to
> test on a development machine but I would like to use any current
> knowledge already established.
> Thanks.
> Lewis
>
>
>
> **
> To unsubscribe, send an Email to: [EMAIL PROTECTED]
> with the word "UNSUBSCRIBE" in the body or subject line.
>
**
To unsubscribe, send an Email to: [EMAIL PROTECTED]
with the word "UNSUBSCRIBE" in the body or subject line.
**
To unsubscribe, send an Email to: [EMAIL PROTECTED]
with the word "UNSUBSCRIBE" in the body or subject line.
