There are also some descent articles on some of the
PHP sites that talk about database normalization. I
look at it like if anything is repetitive it should
probably have it's own table. Not always in every
scenario, but keep in mind that when you move towards
database normalization your queries will most likely
become more complicated also. When I used to store
information in a single table in a database I now find
my self breaking things out quite a bit more, not only
is this faster, especially when you can link things with
integers, but much easier to upgrade and much faster for
programming on many occassions.
Check out www.phpbuilder.com for some basic information
about DB's and such. There are also great articles related
to php. The other thing is sit down and read the pgsql
book located on the postgres site. And when in doubt just
stop by your nearest chat room and ask questions. Most
people are willing to answer.
Hope this helps.
Andy Holman
I-Developit.Com Inc.,
Francisco Reyes wrote:
>
> On Tue, 6 Feb 2001, John Burski wrote:
>
> > I'm looking for a good college-level text that covers general database
> > design and implementation.
>
> Don't know of a good book, but in the mean time.
> Search the web for "normal form".
> Understanding normalization is probably one of the basic things which
> would help you in your designs. I am not saying you should normalize every
> time you design, but if you have an understanding of what that is all
> about you will be able to do better designs.
>
> You may also want to subscribe/read some database newsgroups. I believe
> there is one called comp.database.theory. That may be a good place to ask
> for books too.