Several bugs found in Asp.net data binding (occasionally)

(1) Binding
The first thing worth mentioning is sqldataadapter.
In the 2005 team suit ide
When you throw a data table in the form from the server resource manager, your actions are OK.
Binding normal display normal update deletion normal

At this time, you are wondering what if someone else is using this page to generate concurrent dirty data?

So you config sqldatasource, and in advance, you open the use optimistic concurry
Congratulations, your update + Delete is all voided.

Cause: It seems that the data table value before the change cannot be correctly transmitted to sqldatasource during GV update.
(The @ original_xxx parameter of the update and delete commands is found to be null with the SQL Server event viewer.

It seems to be a gridview bug because other people on the Internet say that datalist and formview do not have this problem.

(2) generated by sqldatasourceCode
The bug is very simple. It cannot be used to intelligently identify long fields.
No matter whether it is text or ntext, there is only one judgment operator in the generated code "=" not even like?

Coming soon: the famous objectdatasouce bug
Objectdatasource: cocould not find a non-generic method '...'