This question is locked. New answers and comments are not allowed.
I see your following sample in Document Explore about Building N-Tier Applications:
using (EntitiesModel dbContext = new EntitiesModel())
{
Car attachedCar = dbContext.AttachCopy(carToDelete);
dbContext.Delete( attachedCar );
dbContext.SaveChanges();
}
using ( EntitiesModel dbContext = new EntitiesModel() )
{
dbContext.AttachCopy( carToUpdate );
dbContext.SaveChanges();
}
My question is what's purpose of AttachCopy method? Whether this is the good practice for delete or update operation?
using (EntitiesModel dbContext = new EntitiesModel())
{
Car attachedCar = dbContext.AttachCopy(carToDelete);
dbContext.Delete( attachedCar );
dbContext.SaveChanges();
}
using ( EntitiesModel dbContext = new EntitiesModel() )
{
dbContext.AttachCopy( carToUpdate );
dbContext.SaveChanges();
}
My question is what's purpose of AttachCopy method? Whether this is the good practice for delete or update operation?
1 Answer, 1 is accepted
0
Hello Jin,
Damyan Bogoev
the Telerik team
The AttachCopy method attaches a copy of an object graph to the context. If a new, deleted or changed instance already exists in the context for an object the operation will fail.
Additional helpful information regarding the functionality can be found here.
Hope that helps.
Damyan Bogoev
the Telerik team
Follow @OpenAccessORM Twitter channel to be the first one to get the latest updates on new releases, tips and tricks and sneak peeks at our product labs!