Hi everybody, I'm newly subscribed so please be gentle :) I have a design problem whose solution seems to be directly linked to the MySQL way of handling joints.
I created a table USER which manages all entities allowed to connect to the system. |---------------| |---------------| |PERSON | |COMPANY | |id_person | |id_company | |id_user | |id_user | |... | |... | |---------------| |---------------| | | | ------------------ | | V V |-------| |USER | |id_user| |... | |-------| A professional told me tables PERSON and COMPANY would slow down the querys (I should by the way move informations of PERSON and COMPANY to USER) and increase upkeep costs. We began to argue as I told queries on USER weren't affected by them (as FK's are placed on PERSON and COMPAGNY). Moreover, my solution is more formal and obeys normalisation. Which solution seems to be better ? Thanks by advance _____________________________________________________________________ Un mot doux à envoyer? Une sortie ciné à organiser? Faites le en temps réel avec MSN Messenger! C'est gratuit! http://ifrance.com/_reloc/m -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
