List:General Discussion« Previous MessageNext Message »
From:Eric Gorr Date:April 2 2005 10:05pm
Subject:Re: [Q] Database design
In-reply-to:
<B99995113B318D44BBE87DC50092EDA914CFB794@nj7460exch006u.ho.lucent.com>
View as plain text  
It took me awhile to understand this, but it does appear to be the 
correct solution in my case. Thank you.


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... ===
Thread
[Q] Database designEric Gorr2 Apr
  • Re: [Q] Database designPeter Brawley2 Apr
    • Re: [Q] Database designEric Gorr2 Apr
      • Re: [Q] Database designPeter Brawley2 Apr
Re: [Q] Database designTom Crimmins2 Apr
  • Re: [Q] Database designEric Gorr2 Apr
RE: [Q] Database designBob)2 Apr
Re: [Q] Database designEric Gorr3 Apr