Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Avoiding multiple cascade paths
Message
 
 
À
21/08/2008 12:56:59
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Conception bases de données
Versions des environnements
SQL Server:
SQL Server 2005
Divers
Thread ID:
01340693
Message ID:
01340839
Vues:
9
I guess you'll have to write another trigger for the RowColumns table to validate ColumnId against the Columns table

>
>I'd tried that but when deleting a row in the Rows table I got a 'The DELETE statement conflicted with the REFERENCE restraint' error.
>?
>Thx,
>Viv
>
>>Keep the FK but set ON DELETE NONE
>>
>>>
>>>Thx. Thought that might be the answer ; got it working for cascading the deletes. But that leaves the other half of the equation : How to prevent insertions in the RowColumns table if the ColumnId doesn't exist in the Columns table ?
>>>
>>>Regards,
>>>Viv
>>>
>>>>You can replace one of ON DELETE CASCADE to RowColumns with a trigger.
>>>>
--sb--
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform