LinqToSql associations bug

  • Thread starter Thread starter Bill McCormick
  • Start date Start date
B

Bill McCormick

I'm currently developing on .NET 3.5 (for an existing back end) and I am
being bitten by an apparent known bug: an issue using LinqToSql and
associations between entity classes that are based on VarChar fields - or
maybe it's association NOT based on int type fields.

Anyway, apparently I can begin using the .NET 4.0 Beta to fix this. Can
anybody here confirm that? My only other option seems to be to re-key a
bunch of DB fields and relationships. Maybe I have another option?

Thanks,


Bill
 
I'm currently developing on .NET 3.5 (for an existing back end) and I am
being bitten by an apparent known bug: an issue using LinqToSql and
associations between entity classes that are based on VarChar fields -
or maybe it's association NOT based on int type fields.

Anyway, apparently I can begin using the .NET 4.0 Beta to fix this. Can
anybody here confirm that? My only other option seems to be to re-key a
bunch of DB fields and relationships. Maybe I have another option?
Click to expand...

I left something out: The bug seems to be where associations between entity
classes are based on a relationship where the field in the parent class is
not the primary key of the table, not if the field is VarChar.
 
Back
Top