Last post Oct 27, 2016 02:09 AM by Jean Sun
Oct 24, 2016 11:19 AM|EnenDaveyBoy|LINK
I am using entity framework, asp.net mvc 5, and I am creating a CMS.
now I have created a number of main elements, lets call on product, and I have seperate a lot of the information for the product in 1-1 table relationships, things like the references, cart information, and other fixed information.
I did this to start mainly to keep thecould information seperatly so I could manage it in developement easier and also if I did an update I wouldn't worry about all the records being destroyed if I messed up only part. I also like using if entity.OtherTable
!= null to validate.
The more complex the design gets I really like the seperatation, but my question is, is this considered inefficient, bad design, are there better ways to control the seperation of information,i know its also ready caused a few issues with includes in the
Any information would be appriciated.
Oct 25, 2016 08:45 AM|Jean Sun|LINK
The more complex the design gets I really like the seperatation, but my question is, is this considered inefficient, bad design, are there better ways to control the seperation of information,i know its also ready caused a few issues with includes in the entity
I think this is based on your actual design. When we design data tables, we need to consider many factors. We can't define that separation is bad design or good design, it all depends on how you use it.
Oct 26, 2016 10:01 AM|EnenDaveyBoy|LINK
Thanks for the information, fair point,i don't suppose you have a source of information I could read to figure it out?
Oct 27, 2016 02:09 AM|Jean Sun|LINK
Could you please show the detail of your database design? I can't tell if your separation is good or bad without knowing your database design.
Separation is a good choice when you design complex database, but too many separation may cause some other issues.
The following link talks about database design best practices , please take it as reference.