Click here to Skip to main content
15,439,373 members
Please Sign up or sign in to vote.
0.00/5 (No votes)

I have a simple database made of 4 entities (User, Application, Market, Category)
I'm coding the Market page but I'm not sure about my choises so:

Is it right to make a Market entity?

Because I thought that Market will be a page, so, an entity of Market will be redundant.

What do you think about?


I'm thinking that designing a Market entity creates more than one market, I need only once, so I'm really numb about.
Updated 27-Aug-11 0:47am
RaisKazi 27-Aug-11 6:56am    
I think their will be only one LINQ Entity Class for "Market", if you have "Market" Table. This may get ambugious with your Market Page Class. Thats the reason, I am suggesting you to rename your Page Class to something else other than "Market".

1 solution

I suggest, you rename your page class to "MarketPage"(or something else than "Market"), this will help you in avoiding redundancy.
Share this answer

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900