blocks|key|1570231|text|在以下位置：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1570232|QuestionModule+o+=+query.First();|code-block|syntax|javascript|1570233|您必须添加以下命令：|1570234|db.QuestionModule.Attach(o);|1570235|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Under:

<pre><code>QuestionModule o = query.First();
</code></pre>

You have to add the following command:

<pre><code>db.QuestionModule.Attach(o);
</code></pre>

blocks|key|1355159|text|确保相关表(即要更新的表)中没有包含null值的列。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1355160|entityMap^0|I|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Ensure that no columns contain <code>null</code> values in the related table (i.e. the table to be updated).

blocks|key|1570401|text|我能够通过在updatepanel回发期间在网格视图和数据源上执行databind()来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1570402|++++protected+void+UpdatePanel1_Load(object+sender,+EventArgs+e)
++++{
++++++++GridView1.DataBind();
++++++++LinqDataSource1.DataBind();
++++}|code-block|syntax|javascript|1570403|每次选择索引更改时，我都会刷新updatepanel，它能够解决冲突。|1570404|希望这能有所帮助。|1570405|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I was able to resolve this issue by executing databind() on the gridview and datasource during updatepanel postback. 

<pre><code> protected void UpdatePanel1_Load(object sender, EventArgs e)
 {
 GridView1.DataBind();
 LinqDataSource1.DataBind();
 }
</code></pre>

I refresh updatepanel each time my selection index changes and it was able to resolve the conflicts.

Hope this helps.

blocks|key|1355367|text|似乎也适用于我的情况。我在内存中构建了一个以前从未提交过的行，它与其他表中的行有几个外键关系。InsertOnSubmit似乎可以工作，但随后的DeleteOnSubmit显示行未找到错误。我没有填充我提交的行中的每个字段，所以我不知道这是否与此有关，但是标记主表的所有非主键列可以消除错误消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1355368|另一个想法是:我认为将列的UpdateCheck策略标记为“Never”意味着它不会被用作乐观并发检查的基础。这将意味着两个用户可以用任何这样的列中的不同数据覆盖给定行，并且冲突不会被detected...meaning，最后提交该行的用户将覆盖前一个用户提交的值。我从各种在线阅读中了解到，一个部分解决方案是在提交之前立即使用Refresh方法来同步任何更改。当然，在行上没有pesimistic锁的情况下，不能保证该行在刷新和提交之间不会更改，但在大多数涉及大型数据库的场景中，这种情况很少见。|1355369|更新:在进一步的回顾中，我认为我发现了一个可能会影响其他人的场景，所以我想我应该分享一下，以防万一。事实证明，我在使用SQL+LINQ时遇到的问题至少有一部分与触发器有关。如果您使用SQL+LINQ提交行，并且您的DBA具有设计用于将信息写入该行中某些列的触发器，则SQL+LINQ模型将在缺省情况下‘始终’确定该行在您上次写入该行后已被更改。我提交的是部分填充的行，而我们的DBA的触发器填充了一些列，因此当我尝试进一步修改代码中的行时，它会根据触发器填充的列检测到更改冲突。我现在正在研究处理这个问题的最好方法，但将这些触发器填充字段更改为使用“当更改时”或“从不”的UpdateCheck策略对我有效。希望能有所帮助。|1355370|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Seemed to work for my situation also. I was building an in memory, never before submitted row which had several foreign key relationships to rows in other tables. The InsertOnSubmit seemed to work but a subsequent DeleteOnSubmit was giving me that row not found error. I was not populating every field in the row I submitted so I don't know if that had anything to do with it but marking all of the main table's non-primary key columns eliminated the error message. 

One further thought: I take it that marking a column's UpdateCheck policy as 'Never' means that it is not used as the basis for optimistic concurency checking. This would imply that two users could write over a given row with different data in any such column and the conflicts would not be detected...meaning the last user to submit the row would overwrite the values of the previous users submission. I gathered from various online reading that one partial solution to this is to use the Refresh method immediately before submission to sync up any changes. Of course with no pesimistic lock on the row there is no guarantee that the row won't still be changed between the Refresh and the Submit but in most scenarios involving large databases this would be rare.

Update: On further review I think I have discovered a scenario that may be affecting others so I thought I would share it just in case. It turns out that at least part of the trouble I have been having with SQL LINQ is related to triggers. It appears that if you submit a row using SQL LINQ and your DBA has triggers designed to write information to some columns in that row then the SQL LINQ model will by default 'Always' determine that the row has been changed since your last write of it. I was submitting partially populated rows and our DBA's triggers are filling in some columns so that when I attempted to further modify the row in our code it sensed a change conflict based on the columns populated by the trigger. I am investigating now the best way to handle this but changing these trigger populated fields to use an UpdateCheck policy of 'When Changed' or 'Never' worked for me. Hope it helps.

blocks|key|1570520|text|我在更新行时遇到了类似的changeconflictexception/“找不到或更改了行”。通过在dbml中重新添加表解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1570521|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had similar changeconflictexception/"Row not found or changed" when updating a row.
Solved it by re-adding the tabbles in the dbml.

blocks|key|1570570|text|问题也可能仅仅是表的DBML定义与数据库定义的状态不一致。我只是从数据库中删除了DBML模型，并将其重新插入，它就起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1570571|希望这对某些人有帮助。|1570572|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The problem could be also simply that the DBML definition of the table is not consistent with the status of the Database definition. I just removed the DBML model and inserted it again from the database, and it worked.

Hope this helps somebody.

blocks|key|1570632|text|出现此错误很可能是因为您的某个字段在Linq+To+SQL设计器和实际数据库中具有不同的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1570633|在我的例子中，这是因为其中一个字段在数据库中是可以为空的，而在设计器中是不可为空的，这使得它在设计器中可以为空，同时也解决了这个问题。|1570634|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You are getting this error quite possibly because one of your fields has something different in the Linq To SQL designer and in the actual database.

In my case, it was because one of the fields was nullable in the database and not nullable in the designer, making it nullable in the designer as well solved the problem immediately.

blocks|key|1355551|text|另外--如果你正在为linqdatasource调用选择方法并手动设置e.result，请确保你也包含了所有的外键值。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1355552|除了这个，其他的对我都没用。|1355553|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Also - if you're calling the selecting method for the linqdatasource and setting e.result manually, make sure you're including any foreignkey values as well. 

Nothing else worked for me but this.

blocks|key|1570765|text|我修复它的方法是:首先更新数据库，然后将网格的新值设置为|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1570766|e.Keys["ColumnOne"]+="new+value"
e.Keys["ColumnTwo"]+="new+value"|code-block|syntax|javascript|1570767|所有这些都是在GridView_RowUpdating事件下完成的。|offset|length|style|CODE|1570768|entityMap^0|0|0|7|K|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The way i fixed it was: First I update the database, then I set the new values for the grid as

<pre><code>e.Keys["ColumnOne"] ="new value"
e.Keys["ColumnTwo"] ="new value"
</code></pre>

All this was done under the <code>GridView_RowUpdating</code> event.

blocks|key|1355721|text|我只是想为任何可能有这个问题的人添加我的场景。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1355722|我们对Linq+to+SQL+dbml使用自定义T4。基本上，我们只是修改了字符串属性的原始get/set，以自动修剪和设置null。|1355723|++++++++get+{+return+_OfficiantNameMiddle.GetValueOrNull();+}
++++++++set+
++++++++{
++++++++++++value+=+value.GetValueOrNull();
++++++++++++if+(_OfficiantNameMiddle+!=+value)+
++++++++++++{
++++++++++++++++_IsDirty+=+true;
++++++++++++++++OnOfficiantNameMiddleChanging(value);
++++++++++++++++SendPropertyChanging("OfficiantNameMiddle");
++++++++++++++++_OfficiantNameMiddle+=+value;
++++++++++++++++SendPropertyChanged("OfficiantNameMiddle");
++++++++++++++++OnOfficiantNameMiddleChanged();
++++++++++++}
++++++++}|code-block|syntax|javascript|1355724|我们的数据库中的遗留数据有一些前导/尾随空格，因此对这些列的任何并发检查都不会导致匹配(它将修整的值与未修剪的数据库值进行比较)。分析SQL，抓取SQL并开始注释WHERE子句中的项，直到它在并发检查期间开始返回一行，这真的很容易。|1355725|幸运的是，我们的表中有一个通过OnValidate(System.Data.Linq.ChangeAction)自动设置的LastUpdatedOn字段。|1355726|++++partial+void+OnValidate(System.Data.Linq.ChangeAction+action)
++++{
++++++++if+(action+==+System.Data.Linq.ChangeAction.Insert)
++++++++{
++++++++++++CreatedBy+=+CurrentUserID;
++++++++++++CreatedOn+=+DateTime.Now;
++++++++++++LastUpdatedBy+=+CreatedBy;
++++++++++++LastUpdatedOn+=+CreatedOn;
++++++++}
++++++++else+if+(action+==+System.Data.Linq.ChangeAction.Update)
++++++++{
++++++++++++LastUpdatedBy+=+CurrentUserID;
++++++++++++LastUpdatedOn+=+DateTime.Now;
++++++++}
++++}|1355727|为了绕过这个问题，我们只需将除主键列和LastUpdatedOn列之外的所有列的并发检查设置为Never。这对我们很有效。|1355728|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|X|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I just wanted to add my scenario for anybody who may have this issue.

We use a custom T4 against our Linq to SQL dbml. We basically just modified the original get/set of string properties to automatically trim and set null.

<pre><code> get { return _OfficiantNameMiddle.GetValueOrNull(); }
 set 
 {
 value = value.GetValueOrNull();
 if (_OfficiantNameMiddle != value) 
 {
 _IsDirty = true;
 OnOfficiantNameMiddleChanging(value);
 SendPropertyChanging("OfficiantNameMiddle");
 _OfficiantNameMiddle = value;
 SendPropertyChanged("OfficiantNameMiddle");
 OnOfficiantNameMiddleChanged();
 }
 }
</code></pre>

Legacy data in our database had some leading/trailing spaces so any concurrency check on these columns failed to result in a match (it was comparing the trimmed value against the non-trimmed database value). It was really easy to profile SQL, grab the SQL and start commenting out the items in the WHERE clause until it started returning a row during the concurrency check.

Luckily, we have a LastUpdatedOn field in our tables that is automatically set via OnValidate(System.Data.Linq.ChangeAction).

<pre><code> partial void OnValidate(System.Data.Linq.ChangeAction action)
 {
 if (action == System.Data.Linq.ChangeAction.Insert)
 {
 CreatedBy = CurrentUserID;
 CreatedOn = DateTime.Now;
 LastUpdatedBy = CreatedBy;
 LastUpdatedOn = CreatedOn;
 }
 else if (action == System.Data.Linq.ChangeAction.Update)
 {
 LastUpdatedBy = CurrentUserID;
 LastUpdatedOn = DateTime.Now;
 }
 }
</code></pre>

In order to bypass the problem, we just set the concurrency check to Never on all columns except the Primary Key columns and LastUpdatedOn column. This worked for us.

blocks|key|1570905|text|我有一个类似的问题，虽然删除和重新添加DBML表/类对一些用户有帮助，但对我来说有点不同，因为我在客户端使用带有分离实体和ListView的WCF。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1570906|如果我使用.Attach(entity)，它会失败-“找不到或更改了行”，但使用.Attach(entity，original)时，它每次都可以工作|1570907|public+void+DeleteTask(Task+task)
++++{
++++++++TwoDooDataContext+db+=+new+TwoDooDataContext();
++++++++db.Tasks.Attach(task,GetTaskByID(task.ID));
++++++++db.Tasks.DeleteOnSubmit(task);
++++++++db.SubmitChanges();
++++}|code-block|syntax|javascript|1570908|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had a similar problem and although deleting and re-adding the DBML table/class helped some users, for me it was a bit different since I'm using WCF with detached entity and a ListView on the client.

If I used the .Attach(entity) it failed - "Row not found or changed"
But when using .Attach(entity, original) it works every time

<pre><code>public void DeleteTask(Task task)
 {
 TwoDooDataContext db = new TwoDooDataContext();
 db.Tasks.Attach(task,GetTaskByID(task.ID));
 db.Tasks.DeleteOnSubmit(task);
 db.SubmitChanges();
 }
</code></pre>

blocks|key|1355786|text|对我来说，是一个枚举列(映射到varchar)导致了这个问题，所以我必须将更新检查通过为never。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1355787|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me it was an enum column (mapped to a varchar) which caused the problem, so I had to pass update check to never.

blocks|key|1355839|text|我绕过了这个问题，确保在更新对象之前立即刷新它。我使用KeepChanges选项执行此操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1355840|++++db.Refresh(System.Data.Linq.RefreshMode.KeepChanges,+employee);|code-block|syntax|javascript|1355841|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I got around this issue, by making sure to refresh my object immediately before updating it. I do this with the KeepChanges option.

<pre><code> db.Refresh(System.Data.Linq.RefreshMode.KeepChanges, employee);
</code></pre>

blocks|key|1355937|text|我遇到的问题是，我在.net框架中有一个DateTime类型，但是我们的数据库字段是DateTime2类型，这是更高精度的数据类型。因此，当我们提交更改时，对象的日期字段与数据库的日期字段仅相差几纳秒，这将导致并发错误。当我们迁移到较新的MSSQL版本并将我们的DateTime字段转换为DateTime2时，就会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1355938|因此，在我们的代码中，我们有：|1355939|++++Obj.DateUpdated+=+DateTime.Now()|code-block|syntax|javascript|1355940|我们将其更改为：|1355941|++++Obj.DateUpdated+=+DateTime.Parse(DateTime.Now.ToString())|1355942|因此，如果您在进行升级和/或迁移后遇到此错误，请检查您的数据类型，尤其是日期字段。|1355943|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

The problem I had was that I had a DateTime type in the .net framework, but our database field was of DateTime2 type, which is higher precision datatype. So when we would submit changes the date fields of the object vs. the DB was just a few nanoseconds off which would cause the concurrency error. This happened when we migrated to a newer MSSQL version and it converted our DateTime fields to DateTime2.

So in our code where we had:

<pre><code> Obj.DateUpdated = DateTime.Now()
</code></pre>

We changed it to:

<pre><code> Obj.DateUpdated = DateTime.Parse(DateTime.Now.ToString())
</code></pre>

So check your datatypes, especially your date fields, if you get this error after making an upgrade and or migration.

blocks|key|1356031|text|这只是列定义不匹配的一个例子。只需从.dbml中删除该表并重新添加即可。确保为具有自动生成数据的列更改auto+generate+value+property+=+true，例如主键或日期时间列。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1356032|entityMap^0|I|5|1F|Z|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

This is just a case of mismatched column definitions. Just remove the table from <code>.dbml</code>and re-add. Make sure to change <code>auto generate value property = true</code> for columns that have auto generated data such as Primary Keys or datetime columns.

blocks|key|1356084|text|正如@dherring79所指出的，这可能是由于数据库和代码之间的精度差异造成的。对我来说，问题是数据库列应该是decimal(10,2)，但它被创建为decimal(18,0)。这是针对money字段的，所以也许我应该使用money列类型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1356085|所以，我存了一美元，比如3.14美元，但是小数点被去掉了。这导致数据库值被更改，并且与C#中的值不匹配。|1356086|希望这能有所帮助。|1356087|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

As @dherrin79 indicated, this can be caused because of a precision variance between the database and the code. For me, the issue was the database column was supposed to be decimal(10,2), but it had been created as decimal(18,0). This was for a money field, so perhaps I should have used the money column type. 

So, I saved a dollar amount, like $3.14 to it, but the decimal was stripped. This resulted in the database value being changed and not matching the value in C#.

Hope this helps.

I am trying to delete a selected gridview row using LINQ (No
LINQDataSource).

When the selection is changed, the detailsview binding is changed
also. I can add a new entry to the database, but when I added this
code to a delete button inside the updatePanel, I got an exception:

<pre><code>try
{ 
 var query = from i in db.QuestionModules 
 where i.QuestionModuleID == QuestionModuleID 
 select i;

 QuestionModule o = query.First();
 db.QuestionModules.DeleteOnSubmit(o);
 db.SubmitChanges();
}
</code></pre>

This is the exception I get:

<pre><code>System.Data.Linq.ChangeConflictException: Row not found or changed. at
System.Data.Linq.ChangeProcessor.SubmitChanges(ConflictMode
failureMode) at
System.Data.Linq.DataContext.SubmitChanges(ConflictMode failureMode)
at System.Data.Linq.DataContext.SubmitChanges() 
</code></pre>

I've had this problem for about a week, and no matter what I do, it is
still there, and the record doesn't get deleted.

Any ideas on what to do?

System.Data.Linq.ChangeConflictException: Row not found or changed

数据库

我正在尝试使用LINQ (No LINQDataSource)删除选定的网格视图行。更改选择时，detailsview视图绑定也会更改。我可以向数据库中添加一个新条目，但是当我将这段代码添加到updatePanel中的delete按钮时，我得到了一个异常：try{               var query = f...

问System.Data.Linq.ChangeConflictException:未找到行或行已更改
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问System.Data.Linq.ChangeConflictException:未找到行或行已更改EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问System.Data.Linq.ChangeConflictException:未找到行或行已更改
EN