Your suspicion for #2 is incorrect; LINQ-to-SQL (like most ORM's) does in fact, know which table has the actual association. Parent-child relationships can have navigation properties on both sides of the association These are taken care of automatically. As for filling the property, that will happen either when loaded explicitly or (if lazy loading is enabled) when you access the property.
Your suspicion for #2 is incorrect; LINQ-to-SQL (like most ORM's) does, in fact, know which table has the actual association. Parent-child relationships can have navigation properties on both sides of the association. These are taken care of automatically.As for filling the property, that will happen either when loaded explicitly or (if lazy loading is enabled) when you access the property.
Sorry, I edited my suspicion #2 a little... for anybody else: Adam is referring to me suspecting that LINQ-to-SQL cannot (automatically) know which table has the actual association. – Lirik Feb 24 at 19:30 @Lirik: The answer is still "yes" ;) – Adam Robinson Feb 24 at 19:33.
Your suspicion for #2 is incorrect; LINQ-to-SQL (like most ORM's) does, in fact, know which table has the actual association. Parent-child relationships can have navigation properties on both sides of the association. These are taken care of automatically.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.