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
columns - if fieldWidgetSize is char(25) - don't call it something 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 database
Don't, however, go overboard with trying to normalize your database.
Don't get me wrong: normalization is good because it saves disk and
memory space (and is quite elegant as well); however, too much
normalization can come at a price in PHP in terms of application speed
and server overhead (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 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 where you have a
fairly
> non-volitile
> and finite set of values, and you plan on searching on this, and don't
want
> to risk the vagaries of a user spelling it a dozen different ways when
> entereing the data....for example - if you have a fixed number of
locations,
> or computer make - i.e.Dell, Compaq, etc. Also, be sure and provide
admin
> pages to update these domain tables...maybe next month your company
starts
> buying ABC-brand pcs - add it to the domain table. When entereing or
> searching - the values in these domain tables populate drop-down
listboxes -
> not left to chance to be entered in a text field....
> Phil J.
> Joni Järvinen - Wandu wrote:
> > Hey
> >
> > I'm quite new to databases so I though I'd ask you for
> > some tips in designing a database.
> >
> > The db that I'm supposed to design holds information
> > about workstations: Motherboard (Motherboard id, # of pci slots,
> > agp slot etc etc.), Harddisks (Size, in what ide and master/slave, etc),
> > the physical location of the workstation and it's hardware configuration
> > etc.
> >
> > So if you could give me some tips and pointers for what tables to create
> > etc I would be grateful.
> >
> > TIA
> >
> > -Joni-
> >
> > --
> > PHP Database Mailing List (http://www.php.net/)
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > To contact the list administrators, e-mail: [EMAIL PROTECTED]
> --
> PHP Database Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
