实体框架的设计？ [英] A design for entity framework?

问题描述

这个设计解决方案是否可以通过实体框架解决？



一个名为car partsv1.0的应用程序有一个用户并且包含一个强类型的关系数据库适用于用户车辆数据的10个汽车零件中的每一个的列。



数据非常易于搜索，因为它位于索引表中。



版本2.0将有多个用户在发布时不同的车辆未知。



以下强类型列模型对于每个新用户和新车的每个可想到的部分，数据可能具有不同的名称。沿着这个新版本的关系强类型列数据库设计模型提出了各种设计选择。



一种方法可能是放弃强类型列。另一种可能是尝试创建通用列并使用抽象映射表来装配新的汽车零件架构。使用数据库搜索数据似乎是一个非常需要的功能，因此尽管我认为这是LINQ的用武之地，但最初在代码中维护数据映射似乎不太理想。



我的问题是：

实体框架在这类问题域中提供什么。

或其他可能适用的解决方案。

Could this design solution be solved by Entity Framework?

An app named "car parts" v1.0 has one user and incorporates a relational database with strongly typed columns for each of the 10 car parts that applies to the user's vehicle data.

The data is very searchable since it is in an indexed table.

Version 2.0 will have multiple users with different vehicles unknown at the time of release.

Following with this strong typed column model for each conceivable part for each new user and new car the data might have different names. Following along the relational strong typed column database design model for this new version brings up various design choices.

One approach might be to abandon strong typed columns. Another might be to attempt to create generic columns and use abstracted mapping tables to post-fit a new car part schema. Using the database to search the data seems to be a highly desired feature so that maintaining the data mapping in code initially appears less desirable although I suppose this is where LINQ comes in.

My questions are:
What does entity framework offer in this type of problem domain.
Or what other solutions might apply.

推荐答案

谢谢谢尔盖，事实证明我的问题是关于SQL Server的混合EAV模式，我对此感激不尽。

Thanks you Sergey, it turns out that my question is about hybrid EAV patterns with SQL Server on which I'd appreciate any further input.

这篇关于实体框架的设计？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！