Advanced modeling topics

DevForce supports more than the simple mapping of tables to entities we've already discussed.  Here we'll briefly discuss more advanced modeling topics using the Entity Data Model (EDM) designer.

Data Providers

DevForce works with any of the ADO.NET data providers which support the Entity Framework.  You can find more information here.

Inheritance

DevForce supports all the forms of inheritance, table mapping and splitting that the Entity Framework supports. 

• Microsoft walkthrough on Table per Hierarchy inheritance mapping
• Microsoft walkthrough on Table per Type inheritance mapping
• Microsoft walthrough on mapping an entity to multiple tables

Note that there may be performance implications with some of these techniques.

Stored procedures

DevForce supports stored procedures for both query and create, update and delete actions.

• How to import a stored procedure for query
• How to map insert, update and delete functions to stored procedures
• Code sample on stored procedures
• Stored procedure queries in DevForce
  
  

Complex types

We've discussed complex types separately in some detail, but here's additional information.

• How to create a Complex Type
  
  

Many-to-many

DevForce supports many-to-many relationships in the same way as the Entity Framework.  If the join table in the database contains no extra payload then the EDM Designer defines only an association in place of a "join entity".  If the table contains payload (i.e., additional properties other than the foreign keys) then an entity is created for the table.

• Many-to-many relationships in EF
• Adding and removing with many-to-many navigation properties
• Code sample on many-to-many relationships
  
  

Cascading deletes

DevForce defines the same rules for cascading a delete on a relationship as the Entity Framework does.  When you want to automatically delete all of the child records of a parent when the parent record is deleted you can specify the cascade delete rule.  As with EF, it is strongly recommended that you specify the cascade delete rules in both the conceptual model and the database. The reason for this is that DevForce will delete only the related objects currently loaded into the entity cache.

• Handle cascaded deletes when saving
• Code sample on cascading deletes
• Cascading deletes in EF
  
  

Concurrency

DevForce supports optimistic concurrency via the Entity Framework.  The EF allows you to define one or more concurrency properties for your entities; DevForce extends this support by also allowing you to define a concurrency strategy for each.   

• Managing concurrency during a save
• Code sample on handling concurrency conflicts
  
  

Learn more

• Learn more about the EDM wizard and designer.
• Descriptions and walkthroughs on mapping and modeling tasks.