Oozooo Posted October 25, 2010 Share Posted October 25, 2010 Hi all, I'm currently developing an website that contains a lot of company profiles. I was wondering what the best database setup would be to save the profile information and to keep it as scalable as possible. Not every company needs the same options. Is is best partice to have 1 company_profile table with the options, and multiple tables for images/reviews connected to that company? -> [company_profile] c_id - c_email - c_opening_time_monday - c_description - etc [company_images] c_id - c_filename [company_review] c_id - c_review OR would it be better to have 1 table with: [company_profile_options] c_id - c_option_type - c_value but then i would have to make the c_value type a long_text to have the ability to store the company description :/ Probably a stupid question but i'm just learning this php mysql thingy Anyone care to help me out ? ---- i see that this is not the right forum for this topic, could someone move it for me ? My apologies Quote Link to comment https://forums.phpfreaks.com/topic/216809-mysql-application-design/ Share on other sites More sharing options...
fenway Posted October 30, 2010 Share Posted October 30, 2010 If there can be multiple entities for a given related record, then multiple tables in the preferred way to go. Quote Link to comment https://forums.phpfreaks.com/topic/216809-mysql-application-design/#findComment-1128488 Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.