Advertisement

01.22.2007 at 03:31PM PST, ID: 22132356
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.8

multiple cascade cycles issue

Asked by andieje in MS SQL Server

Tags: , ,

HI

I have a table called  Request. This represents a request made on a website. This table has 2 foreign keys, both of which link back to the User table and contain a UserID. One is called RequestorID and the other is called AcceptorID. These fields represent the person who made the request and the person who accepted the request respectively.

I have set the table up so that there is a delete and update cascade on the requestorID foreign key. I tried to do the same for the acceptorID foreign key but i got this error message

Introducing FOREIGN KEY constraint 'FK_Request_MyUser_Acceptor' on table 'Request' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.

Is there a way to cascade or is there nothing i can do?

thanks a lot
andreaStart Free Trial
[+][-]01.22.2007 at 11:01PM PST, ID: 18372901

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: MS SQL Server
Tags: cascade, multiple, cycles
Sign Up Now!
Solution Provided By: imran_fast
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20081112-EE-VQP-44 - Hierarchy