I want to thank *everyone* that sent me a reply on this matter. Trouble
is you guys' messages were so good that I have to study the suckers
first before I know if I need to ask for further clarification. So I
might be back in a couple of days ;) Thanks a bunch, guys! Later
--
-duke
Calgary,
else if
it appears elsewhere - and don't change it's type!
Phil J.
- Original Message -
From: "Richard Scott Crawford" [EMAIL PROTECTED]
To: "Phil Jackson" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, April 22, 2001 1:17 AM
Subject: Re: [PHP-DB] Designing a datab
Well to start with, I would examine the nature of the data you want to
store, it's datatype, size, ect. Follow the other reccommendations as to
not repeating data
across tables. I tend to use autonumber fields for keys quite often. Also,
think about what data could go into "domain" tables
(not to mention creating coding nightmares if you're
using your web-based application to enter data into your database as well
as pull information from it).
Original Message
On 4/21/01, 10:10:19 PM, Phil Jackson [EMAIL PROTECTED] wrote regarding
Re: [PHP-DB] Designing a database:
Well
On Sun, Apr 22, 2001 at 01:28:34AM -0500, Phil Jackson wrote:
Good Point, Richard - sensible normalization - if duplicating a value
here and there saves you from having to reference 12 tables instead of
3, yes, by all means. Also, adapting some standards as to using
meaningfull names for
Duke,
The best thing is to get a good book on the subject. There is 1st normal
form, 2nd normal formetc. (quite a few).
I would think that 1st normal form should do (i.e. no repeating groups as in
address1, address2...addressN) Look at how the data relates to each other.
The nature of
Designing DB's is an entire domain of study in itself!
However the rules (guidelines rather) I stick by at present but am open
to new ones as I need them,- are:
* Don't repeat data across tables (leads to 'data redundancy' = more
complex to update the DB)
* If in doubt 'put it' in a new table
So if you could give me some tips and pointers for what tables to create
etc I would be grateful.
You can find a few articles on www.devshed.com about database normalization.
The whole idea is to put every piece of data only once in your database.
And refer to them as an ID. Every ID must be
