Bartis, Robert M (Bob) wrote:
Sounds like you need a 1:N relationship table to hold userInfo separate from either the user or group table. Adding a infoIdentifier would allow the number of rows added for a specific user to be sized based on the specific user needs. This is effect would be the "key" part of a key-value pair, normally associated with associative arrays. The userSpecificInformation would hold the value portion of the information.
UserInfo table: id (pk) user_id (fk) infoIdentifier userSpecificInformation
user table: id (pk) name any other user info only dependant on the user
group table: id (pk) name
usergroup table: user_id (pk) group_id (pk) any info specific to individual user/group combo
UserInfo table: id (pk) user_id (fk) infoIdentifier userSpecificInformation
-- == Eric Gorr ========= http://www.ericgorr.net ========= ICQ:9293199 == "Therefore the considerations of the intelligent always include both benefit and harm." - Sun Tzu == Insults, like violence, are the last refuge of the incompetent... ===
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
