LINQ to SQL - Nullable INT in ForeignKey = "Cannot create an association..."

Question

I have a table that has a primary key that's an INT... I have another table, that has a foreignkey relationship to that first table, but it's a NULLABLE INT.

This is perfectly ok, and 100% acceptable to SQL... however LINQ to SQL is complaining about mismatched types ("int to Nullable[int]").

Error Message: Cannot create an association "Store_People". Properties do not have matching types: "PersonID", "ID".

How do I solve this so that the designer stops yelling at a 100% correct usage of SQL?

Answer 1

I have precisely that situation in a DBML now, and it is working fine.

Primary Key

• Nullable - False
• Primary Key - True
• Server Data type - int NOT NULL IDENTITY
• Type - int (System.Int32)

Foreign Key

• Nullable - Trure
• Primary Key - False
• Server Data type - Int
• Type - int (System.Int32) (actually defined as Nullable in the context.designer.cs file)