I am reading through on page 572 of your book and I was wondering could not this be better handled if the backend of the database handled this when the database was set up with the standard triggers of on delete cascade? I have always been told that handling issues like this at the database level rather than at the front end is or has been always the best way to go.

CREATE TABLE Courses (
CourseID int NOT NULL PRIMARY KEY,
Course VARCHAR(63) NOT NULL UNIQUE,
Code CHAR(4) NOT NULL UNIQUE
);

CREATE TABLE ImarBookCourses (
EntryID int NOT NULL PRIMARY KEY,
BookID int NOT NULL,
Course CHAR(4) NOT NULL,
CourseNum CHAR(3) NOT NULL,
CourseSec CHAR(1) NOT NULL
);
and I establish a foreign key relationship between the two, like this:

ALTER TABLE ImarBookCourses
ADD FOREIGN KEY (Course)
REFERENCES Courses(Code)
ON DELETE CASCADE;

I mean I am just saying. That is all. Kind of different way to approach this matter is it not?

That really depends on the requirements. Do you really want to delete all reviews when you delete a genre? Probably not; you probably want to reassign them to another genre first.

Be aware that if you define cascade behavior at the database level, you also need to define it in the EF model to keep the two in sync. https://www.google.com/#output=searc...w=1920&bih=925

Cheers,

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!