[prev in list] [next in list] [prev in thread] [next in thread] 

List:       php-general
Subject:    RE: [PHP3] Database Design
From:       "Sander Pilon" <sander () 3dnews ! net>
Date:       1999-11-08 14:35:12
[Download RAW message or body]

100% agreed.

However, to do so - or even understand it - one would need a computer
science related education, or an unhealthy affection for boring
database-design books. A lot of people out there don't have that.

Now, don't get me wrong here :) All I'm saying is that I think a lot of
people do PHP stuff in their spare time, as a hobby, and have other daytime
jobs. Most of these people have never heard of normal forms and
normalisation - how can you expect them to use it then?

Sander

-----Original Message-----
From: Dean, John [mailto:DEANJX@mail.aramco.com.sa]
Sent: Monday, November 08, 1999 15:16
To: php3@lists.php.net
Subject: [PHP3] Database Design


Hi Guys,
Recently I have taken a look at the DDL code used in many of the Data Table
used as part of PHP applications. And the one thing that strikes me is that
the writer has unnecessarily worked very hard on the scripts. What I mean is
let the under lying RDBMS do the work. I lot of time and effort could be
save if Data Tables were properly designed. In the DDL I have looked at
nobody has 'normalized' the tables, there is no use of referential
integrity, no check contraints, etc. Good design would save hours of PHP
coding. What about it guys?
This message is meant to open up a debate. It not meant the negatively
critises (flame) anybody, so please don't be offended.
Best Regards
John Dean
In this world without borders or fences
Who needs Windows or Gates?


-- 
PHP 3 Mailing List <http://www.php.net/>
To unsubscribe, send an empty message to php3-unsubscribe@lists.php.net
To subscribe to the digest, e-mail: php3-digest-subscribe@lists.php.net
To search the mailing list archive, go to: http://www.php.net/mailsearch.php3
To contact the list administrators, e-mail: php-list-admin@lists.php.net

[prev in list] [next in list] [prev in thread] [next in thread]