How should I access a computed column in Entity Framework Code First?

by

I have a somewhat of an workaround.

You can only use calculated field on a existing database.

If you add your property to CF object as:

[DatabaseGenerated(DatabaseGeneratedOption.Computed)]
public decimal TotalSources { get; set; }

and if you add a line in your script that will delete information about generation of that database:

DELETE FROM [dbo].[EdmMetadata]

CF will assume it is existing database and it will work, I have just tried.

UPDATE I forgot, if you add property to your Bond entity like this, then in your script you need to alter it to make it calculated, not add it 🙂
You can even manually “synchronize” database and model – at point where you have everything working without this field, add it in model as computed, and in table as calculated. When you delete hash from edm metadata table CF will work without trying to regenerate model with database.

More Related Contents:

  1. Create code first, many to many, with additional fields in association table
  2. EF codefirst : Should I initialize navigation properties?
  3. Decimal precision and scale in EF Code First
  4. Entity Framework Stored Procedure Table Value Parameter
  5. Entity Framework (EF) Code First Cascade Delete for One-to-Zero-or-One relationship
  6. Ignoring a class property in Entity Framework 4.1 Code First
  7. The entity type is not part of the model for the current context
  8. How can I automatically filter out soft deleted entities with Entity Framework?
  9. composite key as foreign key
  10. Implementing Zero Or One to Zero Or One relationship in EF Code first by Fluent API
  11. EF Code-First One-to-one relationship: Multiplicity is not valid in Role * in relationship
  12. Many-to-many mapping table
  13. One to one optional relationship using Entity Framework Fluent API
  14. EF Code First: How to get random rows
  15. Does Entity Framework 4 Code First have support for identity generators like NHibernate?
  16. Entity Framework Code First Lazy Loading
  17. How to declare one to one relationship using Entity Framework 4 Code First (POCO)
  18. How to disable cascade delete for link tables in EF code-first?
  19. Mapping Database Views to EF 5.0 Code First w/Migrations
  20. Entity framework, problems updating related objects
  21. Navigation Property without Declaring Foreign Key
  22. Optimistic concurrency: IsConcurrencyToken and RowVersion
  23. An error occurred while saving entities that do not expose foreign key properties for their relationships
  24. How do I specify that a property should generate a TEXT column rather than an nvarchar(4000)
  25. How to Specify Primary Key Name in EF-Code-First
  26. Entity Framework and multiple schemas
  27. Entity Framework 4.1: Unable to cast from DbQuery to ObjectQuery
  28. The relationship could not be changed because one or more of the foreign-key properties is non nullable
  29. How should I set up my integration tests to use a test database with Entity Framework?
  30. Entity Framework: field of composite key cannot be nullable?

Leave a Comment