A Design for Entity? RRS feed

  • Question

  • 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.
    Thursday, April 17, 2014 6:16 PM


All replies