Re: Multiple Foreign Keys on Same Table
- From: "pb648174" <google@xxxxxxxxxxx>
- Date: 26 Mar 2006 05:44:49 -0800
The whole cascading delete issue is a major pain in the ass that I
can't believe MS didn't fix in SQL 2005. If we can manually write
triggers to do so, the SQL Server should just be able to handle the
*possibility* of cascading paths and just throw an error when there
actually *were* cascading paths.
.
- Follow-Ups:
- Re: Multiple Foreign Keys on Same Table
- From: --CELKO--
- Re: Multiple Foreign Keys on Same Table
- From: Erland Sommarskog
- Re: Multiple Foreign Keys on Same Table
- References:
- Multiple Foreign Keys on Same Table
- From: FreeToGolfAndSki
- Re: Multiple Foreign Keys on Same Table
- From: Tom Moreau
- Re: Multiple Foreign Keys on Same Table
- From: Erland Sommarskog
- Re: Multiple Foreign Keys on Same Table
- From: Tom Moreau
- Multiple Foreign Keys on Same Table
- Prev by Date: LDAP authentication for Yellowfin on SQLserver
- Next by Date: Re: Multiple Foreign Keys on Same Table
- Previous by thread: Re: Multiple Foreign Keys on Same Table
- Next by thread: Re: Multiple Foreign Keys on Same Table
- Index(es):
Relevant Pages
|
Loading