\nAs a continuation of the previous discussion, here's a DELETE of a title row without fetching it from the database:\n<\/p>\n
\npubsEntities model = new pubsEntities();
\ntitles deletetitle = new titles();
\ndeletetitle.title_id = "BU9994";
\ndeletetitle.EntityKey = new EntityKey("pubsEntities.titles", "title_id", "BU9994");
\nmodel.Attach(deletetitle);
\nmodel.DeleteObject(deletetitle);
\nmodel.SaveChanges();\n<\/p>\n
\nIn this case, you need to populate both the property (title_id) that corresponds to the primary key and also populate the EntityKey itself. Attach the object to the store (note that all the original values need not be specified), delete the object from the store, and save the changes. This bit of trickery convinces the ObjectStateManager that the object was in the store all the time, that you'd fetched it from the database. Then you deleted it from the store, so they'll delete it from the database.\n<\/p>\n
\nOf course, if you have associated titleauthor rows, you'll get an error trying to delete that title. As you would in the relational database. Of course, you can put an ON DELETE CASCADE in the database or delete all of the associated rows first. SQL Server 2005 also allows ON DELETE SET NULL and ON DELETE SET DEFAULT, but you relational data model has to allow this; be careful about using these. You can synthesize and delete all the associated rows and the parent in a single round trip if know what the rows keys are in their entirety, but how do you delete a set of rows in a single statement without fetching or knowing all of the primary key pieces (like the associated au_id in titleauthor table)? Better yet…\n<\/p>\n