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 tutorials listed at http://www.artfulsoftware.com/dbresources.html, and/or read http://www.artfulsoftware.com/mysqlbook/sampler/mysqled1ch01.pdf.
PB
-----
Eric Gorr wrote:
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 whose values vary per user.
So basically a sample structure might look like this: (some details intentionally left out)
Database
Table_Group_A # of user columns
Table_Group_A_UserX Column 1 Data Column 2 Data ... Column N Data
One probably incorrect thought on my part is that it would not be necessary to store the usernames in Table_Group_A of those users who belong to that group. But, thinking about it more, it seems like a good idea. My original intent was to simply look for tables named Table_Group_A_* and extract the username from the table name...
Does anyone have any recommends concerning this kind of design? I would like to be able to lay things out in mySQL as cleanly as possible.
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.1 - Release Date: 4/1/2005
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
