Możesz wstawić encję razem z powiązanymi podmiotami lub możesz wstawić encję bez powiązanych podmiotów, odwołując się tylko do istniejących. To zależy od kodu, który piszesz.
Przykład 1:
User user = GetUserFromSomewhere();
using (var context = new MyContext())
{
Order order = new Order();
order.CreatedBy = user;
context.Orders.AddObject(order);
// will put both order and related entity user into Added state
// because user is not attached to the context
context.SaveChanges();
// creates new order and new user and sets the relationship between them
}
Przykład 2:
using (var context = new MyContext())
{
User user = context.Users.SingleOrDefault(u => u.Id == 1);
// query attaches this user to this context
// user is in state Unchanged now
Order order = new Order();
order.CreatedBy = user;
context.Orders.AddObject(order);
// will put the order into Added state but doesn't touch the
// state of already attached related entities -> user remains
// in state Unchanged
context.SaveChanges();
// creates new order with reference to user, but doesn't create new user
}
Przykład 3:
User user = GetUserFromSomewhere();
using (var context = new MyContext())
{
context.Users.Attach(user);
// we attach explicitely to the context telling EF thereby
// that we know that this user exists in the DB
// user is in state Unchanged now
Order order = new Order();
order.CreatedBy = user;
context.Orders.AddObject(order);
// will put the order into Added state but doesn't touch the
// state of already attached related entities -> user remains
// in state Unchanged
context.SaveChanges();
// creates new order with reference to user, but doesn't create new user
}
Edycja
Przykład 4:
int userId = GetUserIdFromSomewhere();
using (var context = new MyContext())
{
var user = new User { Id = userId };
// we create a stub user entity with the correct primary key
// It's not necessary to set other properties
// to only set the relationship to the order
context.Users.Attach(user);
// we attach explicitely to the context telling EF thereby
// that we know that this user exists in the DB
// user is in state Unchanged now
Order order = new Order();
order.CreatedBy = user;
context.Orders.AddObject(order);
// will put the order into Added state but doesn't touch the
// state of already attached related entities -> user remains
// in state Unchanged
context.SaveChanges();
// creates new order with reference to user, but doesn't create new user
}
pokrewne pytanie: http://stackoverflow.com/questions/5449724/entity-framework-code-first-cannot-insert-duplicate-key-in-object-db – Stefan