No foreign keys on the first date.
-
I wrote this little workaround earlier this year. EF complains about an insert where
ParentIdis set, but allows me to set it with an update.// TODO Address this cluster-wtf.
using (var scope = new TransactionScope(TransactionScopeOption.Required, new TransactionOptions { IsolationLevel = IsolationLevel.ReadCommitted }))
{
if (newProject.ParentId != null)
{
// I don't know why I need this, but EF won't insert with a ParentId, but allows me to set it immediately after.
int parentId = newProject.ParentId.Value;
newProject.ParentId = null;
_projectRepository.Insert(newProject);
newProject.ParentId = parentId;
_projectRepository.Update(newProject);
}
else
{
_projectRepository.Insert(newProject);
}
scope.Complete();
} -
I wrote this little workaround earlier this year. EF complains about an insert where
ParentIdis set, but allows me to set it with an update.// TODO Address this cluster-wtf.
using (var scope = new TransactionScope(TransactionScopeOption.Required, new TransactionOptions { IsolationLevel = IsolationLevel.ReadCommitted }))
{
if (newProject.ParentId != null)
{
// I don't know why I need this, but EF won't insert with a ParentId, but allows me to set it immediately after.
int parentId = newProject.ParentId.Value;
newProject.ParentId = null;
_projectRepository.Insert(newProject);
newProject.ParentId = parentId;
_projectRepository.Update(newProject);
}
else
{
_projectRepository.Insert(newProject);
}
scope.Complete();
}Assuming this is a SQL Server connection, I don't think you can lay this directly at SQL's door, but you might want to see if triggers are involved and see what they do on insert/update. Maybe the update trigger on the child will insert the parentID in the parent table if it doesn't exist? No, that doesn't make sense, the update should fail with a foreign key constraint failure before it reaches the trigger. So, when it complains, what is its complaint?
-
Assuming this is a SQL Server connection, I don't think you can lay this directly at SQL's door, but you might want to see if triggers are involved and see what they do on insert/update. Maybe the update trigger on the child will insert the parentID in the parent table if it doesn't exist? No, that doesn't make sense, the update should fail with a foreign key constraint failure before it reaches the trigger. So, when it complains, what is its complaint?
Something long winded about referential integrity.
-
I wrote this little workaround earlier this year. EF complains about an insert where
ParentIdis set, but allows me to set it with an update.// TODO Address this cluster-wtf.
using (var scope = new TransactionScope(TransactionScopeOption.Required, new TransactionOptions { IsolationLevel = IsolationLevel.ReadCommitted }))
{
if (newProject.ParentId != null)
{
// I don't know why I need this, but EF won't insert with a ParentId, but allows me to set it immediately after.
int parentId = newProject.ParentId.Value;
newProject.ParentId = null;
_projectRepository.Insert(newProject);
newProject.ParentId = parentId;
_projectRepository.Update(newProject);
}
else
{
_projectRepository.Insert(newProject);
}
scope.Complete();
}Do you have an insert trigger behind this table in the database by any chance? It would seem to be consistent.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
Something long winded about referential integrity.
-
Do you have an insert trigger behind this table in the database by any chance? It would seem to be consistent.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
No. The table is created by EF Code First, nothing but the table itself. Not even indexes but for the PK. I think it's something to do with EF trying to also save another child of the same parent, and clashing somewhere far away.
-
I wrote this little workaround earlier this year. EF complains about an insert where
ParentIdis set, but allows me to set it with an update.// TODO Address this cluster-wtf.
using (var scope = new TransactionScope(TransactionScopeOption.Required, new TransactionOptions { IsolationLevel = IsolationLevel.ReadCommitted }))
{
if (newProject.ParentId != null)
{
// I don't know why I need this, but EF won't insert with a ParentId, but allows me to set it immediately after.
int parentId = newProject.ParentId.Value;
newProject.ParentId = null;
_projectRepository.Insert(newProject);
newProject.ParentId = parentId;
_projectRepository.Update(newProject);
}
else
{
_projectRepository.Insert(newProject);
}
scope.Complete();
}As a suggestion, you could debug into the code using the newly open sourced code - http://entityframework.codeplex.com/[^].
-
I wrote this little workaround earlier this year. EF complains about an insert where
ParentIdis set, but allows me to set it with an update.// TODO Address this cluster-wtf.
using (var scope = new TransactionScope(TransactionScopeOption.Required, new TransactionOptions { IsolationLevel = IsolationLevel.ReadCommitted }))
{
if (newProject.ParentId != null)
{
// I don't know why I need this, but EF won't insert with a ParentId, but allows me to set it immediately after.
int parentId = newProject.ParentId.Value;
newProject.ParentId = null;
_projectRepository.Insert(newProject);
newProject.ParentId = parentId;
_projectRepository.Update(newProject);
}
else
{
_projectRepository.Insert(newProject);
}
scope.Complete();
}with EF, it helps you out and takes care of all the FK IDs for you :) You can fill the nested object and let it handle all the FKs (don't even set the ID properties) ie: parentObject.Project = newProject; _projectRepositroy.Insert(parentObject);
-
with EF, it helps you out and takes care of all the FK IDs for you :) You can fill the nested object and let it handle all the FKs (don't even set the ID properties) ie: parentObject.Project = newProject; _projectRepositroy.Insert(parentObject);
EF should do that, but somewhere something is amiss - probably my fluent mappings - and I had to resort to the manual update you see in the code excerpt.