实体框架错误:AcceptChanges无法继续，因为对象'；的键值与ObjectStateManager中的另一
本文关键字：键值 ObjectStateManager 对象 AcceptChanges 错误 框架 因为 继续 实体 | 更新日期: 2023-09-27 18:15:29
我在使用实体框架4.0时遇到问题。我正在尝试保存一个包含"Segment"对象集合的"Treatment"对象。每当我试图添加/编辑一个治疗对象，在那里我添加了2个或更多的新分段，我会得到以下错误：
已成功提交对数据库的更改，但在更新对象上下文时出错。ObjectContext可能处于不一致的状态。内部异常消息：AcceptChanges无法继续，因为对象的键值与ObjectStateManager中的另一个对象冲突。在调用AcceptChanges之前，请确保键值是唯一的。
这是我正在使用的保存方法。"SegmentID"列是"Segment"的PK，它是一个在数据库中设置为自动递增的整数(MS SQL 2008(。默认情况下，"SegmentID"设置为0，直到它从DB中获得更新的段。
public bool Save(Treatment myTreatment)
{
bool result = false;
using (tamcEntities db = new tamcEntities())
{
// IF NEW TREATMENT, CREATE IT AND ADD TO DB
if (myTreatment.Treatment_ID == 0)
{
db.Treatments.AddObject(myTreatment);
result = (db.SaveChanges() != 0);
}
// IF EXISTING TREATMENT, FIND EXISTING TREATMENT IN DB, AND UPDATE IT
else
{
List<string> treatmentIncludes = new List<string>();
treatmentIncludes.Add("Segments");
Treatment myTmt = (from x in db.Treatments
where x.Treatment_ID == myTreatment.Treatment_ID
select x).WithIncludes(treatmentIncludes).FirstOrDefault();
if (myTmt != null)
{
myTmt.Comment = myTreatment.Comment;
myTmt.Cost = myTreatment.Cost;
myTmt.CostItemDrain = myTreatment.CostItemDrain;
myTmt.CostItemE2E = myTreatment.CostItemE2E;
myTmt.CostItemEnhan = myTreatment.CostItemEnhan;
myTmt.CostItemEnv = myTreatment.CostItemEnv;
myTmt.CostItemGuard = myTreatment.CostItemGuard;
myTmt.CostItemOther = myTreatment.CostItemOther;
myTmt.CostItemPed = myTreatment.CostItemPed;
myTmt.CostItemSub = myTreatment.CostItemSub;
myTmt.CostItemTraffic = myTreatment.CostItemTraffic;
myTmt.CostItemUtl = myTreatment.CostItemUtl;
myTmt.Create_DateTime = myTreatment.Create_DateTime;
myTmt.Create_Entity = myTreatment.Create_Entity;
myTmt.Create_User = myTreatment.Create_User;
myTmt.Description = myTreatment.Description;
myTmt.Improvement_Type = myTreatment.Improvement_Type;
myTmt.Jurisdiction = myTreatment.Jurisdiction;
myTmt.Last_Update_DateTime = myTreatment.Last_Update_DateTime;
myTmt.Last_Update_Entity = myTreatment.Last_Update_Entity;
myTmt.Last_Update_User = myTreatment.Last_Update_User;
myTmt.Life_Expectancy = myTreatment.Life_Expectancy;
myTmt.MDOTJobID = myTreatment.MDOTJobID;
myTmt.Planned = myTreatment.Planned;
myTmt.Project_Classification = myTreatment.Project_Classification;
myTmt.ProjectID = myTreatment.ProjectID;
myTmt.Quantity = myTreatment.Quantity;
myTmt.SurfaceTypeAfter = myTreatment.SurfaceTypeAfter;
myTmt.tmp_treat = myTreatment.tmp_treat;
myTmt.Treatment_Date = myTreatment.Treatment_Date;
myTmt.Unit_of_Measure = myTreatment.Unit_of_Measure;
// DELETE MISSING SEGMENTS THAT ARE NO LONGER PART OF THE TREATMENT
List<int> segmentIDsToKeep = myTreatment.Segments.Select(x => x.SegmentID).ToList();
myTmt.Segments.Where(x => !segmentIDsToKeep.Contains(x.SegmentID)).ToList().ForEach(x => db.Segments.DeleteObject(x));
// ITERATE OVER EACH SEGMENT AND INSERT OR UPDATE IT
foreach (Segment s in myTreatment.Segments)
{
if (!string.IsNullOrWhiteSpace(s.PR) && !string.IsNullOrWhiteSpace(s.BMP.ToString()) && !string.IsNullOrWhiteSpace(s.EMP.ToString()))
{
Segment mySegment = new Segment();
// IF EXISTING SEGMENT, FIND EXISTING SEGMENT IN DB, AND UPDATE IT
if (s.SegmentID != 0)
{
mySegment = (from x in myTmt.Segments
where x.SegmentID == s.SegmentID
select x).FirstOrDefault();
}
mySegment.ActualLength = s.ActualLength;
mySegment.BMP = s.BMP;
mySegment.Create_DateTime = s.Create_DateTime;
mySegment.Create_Entity = s.Create_Entity;
mySegment.Create_User = s.Create_User;
mySegment.EMP = s.EMP;
mySegment.HasRequiredHPMS = s.HasRequiredHPMS;
mySegment.Lanes = s.Lanes;
mySegment.Last_Update_DateTime = s.Last_Update_DateTime;
mySegment.Last_Update_Entity = s.Last_Update_Entity;
mySegment.Last_Update_User = s.Last_Update_User;
mySegment.PASER_Rating = s.PASER_Rating;
mySegment.PR = s.PR;
mySegment.RoadName = s.RoadName;
mySegment.SurfaceType = s.SurfaceType;
mySegment.Treatment_ID = s.Treatment_ID;
mySegment.Version = s.Version;
// If the BMP is greater than the EMP, swap them.
if (mySegment.BMP > mySegment.EMP)
{
decimal tempBMP = mySegment.BMP;
decimal tempEMP = mySegment.EMP;
mySegment.BMP = tempEMP;
mySegment.EMP = tempBMP;
}
// IF NEW SEGMENT, ADD IT
if (s.SegmentID == 0)
{
myTmt.Segments.Add(mySegment);
}
}
}
result = (db.SaveChanges(SaveOptions.AcceptAllChangesAfterSave) != 0);
}
}
}
return result;
}
我在Oracle表中插入行时遇到了同样的错误，解决了将edmx文件编辑为xml的问题(右键单击，用..打开，xml编辑器(，并将StoreGeneratedPattern="Identity"添加到表定义中。
之前
<Property Name="ID" Type="number" Nullable="false" Precision="38" Scale="0" />
之后
<Property Name="ID" Type="number" Nullable="false" Precision="38" Scale="0" StoreGeneratedPattern="Identity" />
问题是您在上下文中两次分配相同的Segment键，这会破坏ObjectStateManager。
myTreatment有一个Segment实体的集合，所有这些实体都在被跟踪。现在，当您循环遍历它们时，您将创建另一个Segment，它可能最终与集合中现有的Segment具有相同的密钥：
foreach (Segment s in myTreatment.Segments){
....
Segment mySegment = new Segment(); //NEW OBJECT
if (s.SegmentID != 0)
{
//IN HERE YOU ASSIGN THE SAME KEY TO THE NEW OBJECT
//s.SegmentID == mySegment.SegmentID **CONFLICT**
mySegment = (from x in myTmt.Segments
where x.SegmentID == s.SegmentID
select x).FirstOrDefault();
}
如果您将一列指定为唯一列并尝试将相同的值保存到该列，则会显示错误。如果对你来说可行的话，我可以给你暗示。为了实现这一点，您可以在segments表中添加一个名为"id"的新的自动递增列，并将该列视为关键
table: segment
id- new auto incremented key column
treatment_id
segment_id
entity:
id- key
treatment_id
segment_id
现在执行添加操作。并根据分段的id对分段实体进行编辑和删除操作。
我最近遇到了这个问题，因为我添加了大量默认ID为零的对象，希望数据库和实体框架能够计算出正确的ID，因为我向数据库表添加了序列和触发器。但是，似乎没有，在保存对数据库上下文的更改之前，我必须用正确的ID序列准备对象。
lookupOperation。ID=Sequance。GetSequenceBySequenceName("lo_SEQ"(；