Entity Framework – default values doesn’t set in sql server table

by

This is one of the few issues that are problematic with Entity Framework. Say you have a class that looks like this:

public class MyEntity
{
    // Id is a PK on the table with Auto-Increment
    public int Id { get; set; }

    // CreatedOn is a datetime, with a default value
    public DateTime CreatedOn { get; set; }
}

Now, you want to insert a new element:

using(var context = new YourContext()) 
{
    context.MyEntities.Add(new MyEntity())
}

Entity Framework knows how to handle an auto-increment primary key because of the definition in the EDMX. It will not try to insert a value for the Id property. However, as far as Entity Framework is concerned, CreatedOn has a value: the default DateTime. Because Entity Framework cannot say “well, it has a value but I should ignore it”, it will actively insert the record with the CreatedOn property value, bypassing the default value on your column definition on your table.

There is no easy way to do this. You can either actively set the CreatedOn property to DateTime.Now when you insert that item. Or you can create an interface and an extension method pair:

public interface ICreatedOn
{
    public DateTime CreatedOn { get; set; }
}

public partial class MyEntity : ICreatedOn
{

}

public static TEntity AsNew<TEntity>(this TEntity entity) where TEntity : ICreatedOn
{
    if(entity != null)
        entity.CreatedOn = DateTime.Now;

    return entity;
}

using(var context = new YourContext()) 
{
    context.MyEntities.Add(new MyEntity().AsNew())
}

Edit: To expand on this point, the reason why this is an unresolvable issue is because of the meaning behind an autoincrement field and a field with a default value constraint. An auto-increment field should, by definition, always be handle by the server, using a seed and all that jazz. You cannot specify a value for an auto-increment field on an insert unless you have used SET IDENTITY INSERT ON. A default value, however, is just a hint that say “if I don’t specify any value, use this”. Because value types in .NET cannot be null, there will always be a value and Entity Framework cannot infer that the default value for that field, at that time, means that you want it to be defaulted on the SQL server.

More Related Contents:

  1. How do parameterized queries help against SQL injection?
  2. Entity Framework 4 – AddObject vs Attach
  3. Entity Framework Join 3 Tables
  4. Entity Framework Timeouts
  5. EF Including Other Entities (Generic Repository pattern)
  6. Entity Framework 4 Delete Object from entity collection
  7. Entity Framework/Linq EXpression converting from string to int
  8. Why does the Contains() operator degrade Entity Framework’s performance so dramatically?
  9. Adding stored procedures complex types in Entity Framework
  10. Entity Framework Thread Safety
  11. The result of a query cannot be enumerated more than once
  12. SqlDataSourceEnumerator.Instance.GetDataSources() does not locate local SQL server 2008 instance
  13. Entity Framework/Linq to SQL: Skip & Take
  14. The object cannot be deleted because it was not found in the ObjectStateManager
  15. Entity Framework – Add Navigation Property Manually
  16. Entity Framework – Invalid Column Name ‘*_ID”
  17. How should I multiple insert multiple records?
  18. C# SqlCommand – cannot use parameters for column names, how to resolve?
  19. Received an invalid column length from the bcp client for colid 6
  20. Entity Framework Include() is not working
  21. How can I convert ticks to a date format?
  22. EF4 Code First: how to add a relationship without adding a navigation property
  23. String.Equals() not working as intended
  24. Entity Framework 4: How to find the primary key?
  25. How to Refresh DbContext
  26. Add the where clause dynamically in Entity Framework
  27. Is it possible to prevent EntityFramework 4 from overwriting customized properties?
  28. Entity Framework Code First naming conventions – back to plural table names?
  29. Linq to Entities : using ToLower() on NText fields
  30. Entity Framework – Eager loading of subclass related objects

Leave a Comment