Re: [PHP] Re: Where to start!


"Richard Heyes" <richardh@xxxxxxxxxxx> wrote in message
news:481EDD2C.5030209@xxxxxxxxxxxxxx
Tony Marston wrote:
"Richard Heyes" <richardh@xxxxxxxxxxx> wrote in message
news:481ED03B.7090200@xxxxxxxxxxxxxx
The database must be properly normalised otherwise it
will be difficult to get at the data you need in an efficient manner.
Not true. If your needs are simple for example, normalisation can
increase the complexity of a schema, hence increasing development time
needed. Sometimes for example you could use something like a SET type,
and search for something in it using FIND_IN_SET().

I disagree. The database should ALWAYS be normalised to at least the 3rd
normal form. Sometimes going beyond that to 4NF, 5NF or 6NF becomes too
complex.

Sometimes it's just a waste of time. If your site isn't that busy, and
speed isn't crucial, why waste the time using a more complicated database
structure?

I do not agree that creating a database which is normalised to3NF is a waste
of time. On the contrary, a totally un-normalised database is nothing but a
problem waiting to bite you in the a**e. Computer systems have a habit of
growing over time, and if you don't follow the rules of normalisation your
database will end up as the biggest bottleneck.

Anyone who doesn't know how to reach 3NF shouldn't be designing databases.

--
Tony Marston
http://www.tonymarston.net
http://www.radicore.org


--
Richard Heyes

+----------------------------------------+
| Access SSH with a Windows mapped drive |
| http://www.phpguru.org/sftpdrive |
+----------------------------------------+


.

Relevant Pages

  • Re: Combo Box Help - Stuck Newbie?
    ... table it's appearent the that you do not understand normalisation. ... database normalisation and modeling data structures with entity ... better suited to a query. ... I've read through access help and the following link before posting ...
    (comp.databases.ms-access)
  • Re: New arrivals (II)
    ... Apart from the theoretical advantage of not getting burned ... My usual advice on normalisation is to keep databases as close as ... I also notice that database people seem to expect the database to take care ... problems maintaining such a thing? ...
    (uk.rec.sheds)
  • Re: Normalization and AVG across columns
    ... columns (Proposal Phase Rating, Preconstruction Phase Rating, etc.) ... This is a bit of database theory that covers normalisation Forget that you are using Access for a while, because Access 12 might have new features. ... you need to answer these questions before you commit to a database design. ...
    (comp.databases.ms-access)
  • Re: Rule when primary key is needed?
    ... When you create a table that is part of a "relational" database. ... If you are talking about lookup values for a main table then you should ... part of the normalisation process is to choose the primary key for the data ... normalisation which can only cause you trouble in the long run. ...
    (microsoft.public.access.gettingstarted)
  • Re: [PHP] Re: Where to start!
    ... If your needs are simple for example, normalisation can increase ... the complexity of a schema, ... Sometimes it's just a waste of time. ...
    (php.general)