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 r
mailto:[EMAIL PROTECTED]
Sent: Saturday, April 02, 2005 2:59 PM
To: Tom Crimmins
Cc: mysql@lists.mysql.com
Subject: Re: [Q] Database design
Tom Crimmins wrote:
> user table:
> id (pk)
> name
> any other user info only dependant on the user
>
> group table:
> id (pk)
> nam
Tom Crimmins wrote:
user table:
id (pk)
name
any other user info only dependant on the user
group table:
id (pk)
name
any other group info only dependant on the group
usergroup table:
user_id (pk)
group_id (pk)
any info specific to individual user/group combo
Yes, if I understand what you are sayin
On Saturday, April 02, 2005 12:48, Eric Gorr wrote:
> Peter Brawley wrote:
>> Eric,
>>
>> If I understand you correctly, you propose to encode user and group
>> info as table names. That's a mistake. To use an RDBMS like MySQL
>> effectively, you want to encode your information as rows of data i
Eric,
You do not want to encode data in table names. Mainly you want to
create the least redundant set representation of your data, realise
that representation as fixed related tables, then use SQL to fill &
query those tables. Do a little reading and play with a few toy designs
before you sta
Peter Brawley wrote:
Eric,
If I understand you correctly, you propose to encode user and group info
as table names. That's a mistake. To use an RDBMS like MySQL
effectively, you want to encode your information as rows of data in
tables whose names and structures do not vary.
Thank you for your c
Eric,
If I understand you correctly, you propose to encode user and group info
as table names. That's a mistake. To use an RDBMS like MySQL
effectively, you want to encode your information as rows of data in
tables whose names and structures do not vary. May I suggest you read
some of the tutor
Not having done much database design in the past, I have what should be
a fairly simple design question.
I usage of mySQL will revolve around a common group + user system. There
can be multiple groups and each group will contain some subset of users.
Each group will have a custom set of data whos
