I have a question very similar to this question, How do you create an extensible data model , regarding the creation of an application using an extensible data model, except for using EF 4.
My requirement is to allow users of my application to extend the data model at runtime on the fly. We are currently building the system and used EF as a DAL layer with POCO classes created from the standard T4 template.
Taking this post from Ayende, http://ayende.com/blog/3498/multi-tenancy-extensible-data-model , as a brief description of the options, we took the xml column option in the table, allowing us to place anything in it without need to recompile.
As I understand it, an extended approach to the table would be better; it seems to work well for CRM dynamics, however, how is this possible when using EF 4 on the fly?
One possible solution to this kind of problem is the EAV template> http://en.wikipedia.org/wiki/Entity-attribute-value_model
, , , , int1, int2,... intn, varchar1, varchar2,..., varcharn .. . DB ( ). SQL Severs Sparse Columns . , . - : varchar1 → Name, int1 → Age ..
sql/ef, , SSRS ( xml).
, .
, " XML" , , XML.