Because one row has a space in the value so the rows are unique but ADO.net must trim when applying the primary key. I know...bad data...but once again...something that can't be changed.
Message from Alex Smotritsky <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM received on 10/24/2005 05:29 PM 10/24/2005 05:29 PM Alex Smotritsky <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM Please respond to "Discussion of advanced .NET topics." <[email protected]> Sent by "Discussion of advanced .NET topics." <[email protected]> To: [email protected] cc: Subject: Re: [ADVANCED-DOTNET] Primary Key Bug I don't get it, why shouldn't that code error? -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Franklin Gray Sent: Monday, October 24, 2005 6:01 PM To: [email protected] Subject: [ADVANCED-DOTNET] Primary Key Bug Anybody noticed that this code errors? Is this fixed in 2.0? Module Module1 Sub Main() Dim DT As New DataTable DT.Columns.Add("Key", GetType(String)) DT.Rows.Add(New Object() {"key1"}) DT.Rows.Add(New Object() {"key1 "}) DT.PrimaryKey = New DataColumn() {DT.Columns("Key")} End Sub End Module =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
