Re: Developing a dating service!

Try to identify most important fields and more commonly used fields and use them in a single table. More table access, more time you are going to take. Somebody correct me if I am wrong here, you can have a as much columns as possible in a single table, so you can stay in a single table access rather than a join or multiple selects. When you have a big table make sure, you define indexes properly (based on the use of the fields). David Newcomb wrote: > Sunny, > > > I've read about database normalisation and using seperate > > tables interlinked so that information can be categorised. > > Should I be using this? Any relevant links / articles? > > Yes, normalisation is a must, to reduce data size and increase flexibliity. > There are loads of books on this subject. > > > Can people please offer me advice on possible pitfalls as > > well as the database design tips which I can use for such a > > service?? > > One thing I wish I had known before starting a database project: > Give all the fields in all tables a unique name. > eg create table regested_users { rus_userid, rus_username,rus_passwd } > create bought_item { bit_itemid, bit_rususerid, ... } > now when you use: > select rus_username > from bought_item > where rus_userid = bit_rususerid > and bit_itemid = 24; > you do not have to alias the tables to get the correct fields > > > ANY help would be appreciated!! > > Download a program called phpMyAdmin which is a web front-end > to MySQL - striaght forward and simple to use. > > Just a couple of things to thing about. > > David. > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > For additional commands, e-mail: php-general-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net