3

我正在设计一个数据库模式，但我被困在一个部分。下面是我的架构的简化版本。有人可以解释为什么下面的SQL：

CREATE TABLE Users (
  UserID INT NOT NULL PRIMARY KEY,
  FName VARCHAR(64) NOT NULL,
  LName VARCHAR(64) NOT NULL,
  UName VARCHAR(64) NOT NULL UNIQUE,
  PWord CHAR(32) NOT NULL,
  Role VARCHAR(13) NOT NULL
);

...

CREATE TABLE Sale (
  SaleID INT NOT NULL PRIMARY KEY,
  Book INT NOT NULL REFERENCES Books(BookID) ON DELETE NO ACTION,
  Merchant INT NOT NULL REFERENCES Users(UserID) ON DELETE CASCADE,
  Upload DATETIME NOT NULL,
  Sold BIT NOT NULL,
  Price DECIMAL(10, 2) NOT NULL,
  Condition VARCHAR(9) NOT NULL,
  Written BIT NOT NULL,
  Comments VARCHAR(8000) NULL
);

...

CREATE TABLE Purchases (
  PurchaseID INT NOT NULL PRIMARY KEY,
  Buyer INT NOT NULL REFERENCES Users(UserID) ON DELETE CASCADE,
  Merchant INT NOT NULL REFERENCES Users(UserID) ON DELETE NO ACTION,
  Sale INT NOT NULL REFERENCES Sale(SaleID) ON DELETE CASCADE UNIQUE,
  Time DATETIME NOT NULL
);

...导致此错误，以及如何克服它：

Msg 1785, Level 16, State 0, Line 38
Introducing FOREIGN KEY constraint 'FK__Purchases__Sale__25869641' on table
'Purchases' may cause cycles or multiple cascade paths. Specify ON DELETE
NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.

ON DELETE CASCADE如果可能的话，我想保留Purchases.Sale属性。

感谢您的时间。

4

1 回答 1

4

很可能是因为您从两个不同的表中引用“用户” - 购买中的买家和销售中的商家。数据库可能没有意识到这两个记录永远不会相同 - 但它知道它是同一个表，因此抱怨级联的潜在问题。

于 2012-11-19T02:42:35.477 回答