Home/ Questions/Q 8035299
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T02:16:17+00:00

I’m using ASP.Net 4 EF 4.3.1 Code First Migrations. I have an existing model

  • 0

I’m using ASP.Net 4 EF 4.3.1 Code First Migrations.

I have an existing model class. I’ve added a property to it:

public DateTime LastUpdated { get; set; }

When I run update-database -force -verbose I get:

ALTER TABLE [MyTable] ADD [LastUpdated] [datetime] NOT NULL DEFAULT
‘0001-01-01T00:00:00.000’
System.Data.SqlClient.SqlException
(0x80131904): The conversion of a varchar data type to a datetime data
type resulted in an out-of-range value.
The statement has been terminated.

I’m going to guess this relates to the implied default value being used in the generated SQL – it would appear to be complaining that the varchar it used to initialize things is data lost.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The answer to this problem of not being able to add a non-null DateTime column is the same as the problem of getting 2 default values specified for a DateTime column:
    EF 4.3.1 Migration Exception – AlterColumn defaultValueSql creates same default constraint name for different tables

    That is, it’s been broken a long time, and you can workaround it by migrating with it nullable:

    public DateTime? LastUpdated { get; set; }

PM> update-database

    Then migrate again with it not null to get where you intended:

    public DateTime LastUpdated { get; set; }

PM> update-database
    • 0