PHP Geek needs Database Design Assistance -


like developers think striving create optimal code , database schemas.

however - ive got feeling, im on engineering database schema want create.

i have web app that, in short space of time, hold lot of users. users in form of customers, suppliers, system users. in industry grow rapidly.

in previous schemas have users separated in different tables.

however, thinking of going down route of having 1 table called: people.

there these tables:

people, contact details, residences

they related via pivottables ie: pivotcontacts pivotresidences.

my question considered good/bad design.? on thinking, on engineering simple setup.

the table people grow exponentially , hold alot of data - , other tables relate it.

i welcome opinions.

will design scale 100 thousand records , maintain moderate speed.? * start 1000 records , grow approx 100,000 in 1 year.

for users can log-in, , maybe traced (last login, failed password retries) optimal have small table , maybe separate table writing (distinction between reading , writing data).

any table people in general has tendency collect tremendous number of fields. functional distinctions kept in different tables keep data tidy, indexing on suppliers table nicer/maybe more optimal, changes supplier data. sql joins manageable, , done sql views.

so go thin base table people , 1:1 tables supplierpeople, systemusingpeople , on. , consider changes happen: how tables updated, inserted into, being read.

also consider having modify database scheme, adding field.


Popular posts from this blog

How to calculate SNR of signals in MATLAB? -

c# - Attempting to upload to FTP: System.Net.WebException: System error -

ios - UISlider customization: how to properly add shadow to custom knob image -