Oh my. There are many ways go about creating a community, but a database for Each User? That's pure insanity.
Try making perhaps a table for each user, or maybe (depending on what kind and how much user data you're keeping) use one single table for all users. Read up on Database Normalization for some good design pointers: http://home.earthlink.net/~billkent/Doc/simple5.htm --- Scott Hurring Systems Programmer EAC Corporation [EMAIL PROTECTED] Voice: 201-462-2149 Fax: 201-288-1515 > -----Original Message----- > From: Hawk [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, June 05, 2002 6:04 PM > To: [EMAIL PROTECTED] > Subject: [PHP] Need some suggestions about "community" :) > > > Just for fun I, and a few friends were going to make a > community, started > about an hour ago :) > Haven't started with the design or anything yet, but I was > thinking how the > best way to handle users would be, or atleast what you can > recommend, first > I thought about having a database with users, and one with > messages and > stuff, and then I thought it might be smoother to create a > database for each > user, and store all his/her things in it, what do you think? > If there is any other good way, I'm also open for suggestions :) > > Håkan > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
