CURRENT_TIMESTAMP defaults to "null" value, possible reasons?

Asked Jul 22 '14 at 11:45

Active Jul 22 '14 at 11:55

Viewed 82 times

So if I run a virtual instance of IIS on localhost to test some site, I have a datebase field with a default CURRENT_TIMESTAMP that upon insertion always defaults to 1/1/0001 12:00:00 AM, which is, as I understand, the null-like value for DateTime in these scenarios.

Why is this happening? Can't I get the actual time and date to go in this field?

I've tried using getdate(), sysdatetime() and whichever else alternatives and it's the same thing.

The field in the C# code is:

public DateTime LastModification { get; set; }

Any workaround around this?

I'm using the correct mappings as per msdn

edited Jul 22 '14 at 11:55

asked Jul 22 '14 at 11:45

user3046061

Are you using ORM? Which one? – Andrei Jul 22 '14 at 11:49
possible duplicate of [SQL Server automatic update datetimestamp field](http://stackoverflow.com/questions/5744067/sql-server-automatic-update-datetimestamp-field) – Kenan Zahirovic Jul 22 '14 at 11:51
I don't need a trigger for multiple operations. Just INSERT, so only one default possible. – user3046061 Jul 22 '14 at 11:54
@user3046061, can you post the mapping class which contains the field in question? – Andrei Jul 22 '14 at 11:54
@user3046061, seems [this](https://entityframework.codeplex.com/discussions/471061) is what you are facing – Andrei Jul 22 '14 at 12:03
That explains it. Post an answer with this so I can accept it. – user3046061 Jul 22 '14 at 12:09

CURRENT_TIMESTAMP defaults to "null" value, possible reasons?

0 Answers0