G
Gunnar Mohr
Hi,
- occurs with .Net 2.0 Beta 2 -
I have a typed-DataSet and some DataAdapters to provide the tables for the
DataSet. When I create the stored-procedures with the DataAdaper-Wizard for
a table with a Guid column, which can be NULL, the Wizard generates a wrong
Script. (only when "use optimistic concurrency" is true).
If you look at the script, the following part of the where-clause is faulty
....((@IsNull_FieldName = 1 AND [FieldName] IS NULL) OR ([FieldName] =
@Original_FieldName))...
(FieldName is defined as uniqueidentity, allow NULL)
obviously @IsNull_FieldName = 1 is wrong, because 1 is an Integer and not a
uniqueidentity.
But how to fix that?
regards Gunnar
- occurs with .Net 2.0 Beta 2 -
I have a typed-DataSet and some DataAdapters to provide the tables for the
DataSet. When I create the stored-procedures with the DataAdaper-Wizard for
a table with a Guid column, which can be NULL, the Wizard generates a wrong
Script. (only when "use optimistic concurrency" is true).
If you look at the script, the following part of the where-clause is faulty
....((@IsNull_FieldName = 1 AND [FieldName] IS NULL) OR ([FieldName] =
@Original_FieldName))...
(FieldName is defined as uniqueidentity, allow NULL)
obviously @IsNull_FieldName = 1 is wrong, because 1 is an Integer and not a
uniqueidentity.
But how to fix that?
regards Gunnar