Entity Framework Code First Using Guid as Identity with another Identity Column

by

This ended up working for me, Entity Framework 5.

  1. Turn off automatic migrations
  2. Migrate to create the initial table, no frills

  3. Declare the ClusterId as Identity (annotation)

    [DatabaseGenerated(DatabaseGeneratedOption.Identity)]
public override int ClusterId { get; set; }

  4. Migrate

  5. Declare the pk property Id as Identity after the other one has been updated

    [DatabaseGenerated(DatabaseGeneratedOption.Identity)]
public override Guid Id { get; set; }
    • bonus: EF seems to assume Id is primary key, so you don’t need [Key, Required]

  6. Create the migration code like add-migration TrickEfIntoAutogeneratingMultipleColumns

  7. In the Up() method, in the AlterColumn statement, tell the database to autogenerate the GUID by declaring the defaultSqlValue
    • AlterColumn(theTable, "Id", c => c.Guid(nullable: false, identity: true, defaultValueSql: "newid()"));
  8. Migrate

This seems to “trick” EF, in the sense that it assumes both columns are identities and reacts accordingly. During migration, it tries to make another column an identity, but seemingly doesn’t care when that silently fails — you end up with one marked as Identity and the other with a default value.

During normal code operation, when EF goes through the SaveChanges/ChangeTracking steps, because it sees the Id property as an Identity it does it’s whole “assign temporary key” thing, so that it’s not trying to use the default 0000000… value, and instead lets the database generate it using the default value function you specified.

(I would have thought annotating this field as Computed would have accomplished the same thing, but…the errors I mentioned in the question…boo…)

And, because the ClusterId field is also an Identity in code, and really is an Identity in the database, it autoincrements as well.

More Related Contents:

  1. Debug code-first Entity Framework migration codes
  2. EntityFramework code-first custom connection string and migrations
  3. Improve navigation property names when reverse engineering a database
  4. EF5 Code First Enums and Lookup Tables
  5. Mapping Database Views to EF 5.0 Code First w/Migrations
  6. Code-first vs Model/Database-first [closed]
  7. Entity Framework: One Database, Multiple DbContexts. Is this a bad idea? [closed]
  8. What’s the difference(s) between .ToList(), .AsEnumerable(), AsQueryable()?
  9. Reset Entity-Framework Migrations
  10. Unique Key constraints for multiple columns in Entity Framework
  11. Entity Framework 6 Code first Default value
  12. Batch update/delete EF5
  13. Multiple DB Contexts in the Same DB and Application in EF 6 and Code First Migrations
  14. EF Code First “Invalid column name ‘Discriminator'” but no inheritance
  15. Should I enable or disable dynamic proxies with entity framework 4.1 and MVC3?
  16. Entity Framework loading child collection with sort order
  17. EF5 Code First – Changing A Column Type With Migrations
  18. Value cannot be null. Parameter name: entitySet
  19. There is already an object named in the database
  20. mapping private property entity framework code first [duplicate]
  21. MVC3 and Code First Migrations – “model backing the ‘blah’ context has changed since the database was created”
  22. EF Migrations: Rollback last applied migration?
  23. How to create index in Entity Framework 6.2 with fluent configuration
  24. How can I disable migration in Entity Framework 6.0
  25. Mocking or faking DbEntityEntry or creating a new DbEntityEntry
  26. How to use Entity Framework to map results of a stored procedure to entity with differently named parameters
  27. DbContext AutoDetectChangesEnabled set to false detecting changes
  28. Best way to incrementally seed data in Entity Framework 4.3
  29. AutomaticMigrationsEnabled false or true?
  30. Entity framework code first delete with cascade

Leave a Comment