Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a Linq-To-SQL mapping to a column in a SQL table.
This column is type DateTime with default mapping / binding of getdate().
The problem is that Linq-To-SQL tries to insert 12/1/0001 12:00 AM instead of letting SQL do its thing and insert getdate().
Is there a way around this?
Additionally, if the column is allowed to be null, why does ‘Linq-to-SQL’ try to insert a default value?
This might help (scroll up a wee little bit). It talks of setting the IsDbGenerated and AutoSync properties, which tell the data context that the value is generated at the DB and how the value in the L2SQL object should be synced with the value in the database.
I think my google fu is low today, I’m positive I’ve read a good article/blog post about this, but I cannae find it again.