Jump to content

Recommended Posts

I have developed an application that I was soley planning on using for internal use; however, the idea has come up to release it for general use (within my companies territory). The application has several tables, for example a members, products, categories, etc. My question is, should I have a unique member (or company) id and have all the rows held in each table. Or, have different tables for each company with a unique prefix, or have a completely seperate database for each company? The table that will hold the most data is the products table, around 1500+ products per company. Another concern of mine is security, would it be better to separate the data all together into separate tables or databases?

Thanks!
Link to comment
https://forums.phpfreaks.com/topic/28680-database-layout/
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.