Developer Forums | About Us | Site Map
Search  
HOME > TUTORIALS > DATABASES > POSTGRESQL TUTORIALS > PRACTICAL DATABASE DESIGN, PART 1


Sponsors





Useful Lists

Web Host
site hosted by netplex

Online Manuals

Practical database design, Part 1
By Philipp K. Janert - 2004-02-25 Page:  1 2 3 4

Keys and datatypes

What are the best choices when designing the schema for a relational database? What is the rationale in deciding in favor of one and against some other alternative? Given the amount of vendor-specific recommendations, it is all too easy to overlook basic relational database fundamentals. In this first of two parts, author Philipp K. Janert talks about simple and complex datatypes, and about primary and foreign keys -- the plumbing that holds the entire database together.

In this series, I discuss some general best practices that I have found to be particularly helpful. Nothing in it is specific to any one vendor's product and everything should, therefore, be applicable, regardless of which database implementation is being used. In this frist part of the article, I want to talk about both simple and complex datatypes, and about primary and foreign keys, which are the plumbing that holds the entire database together.



View Practical database design, Part 1 Discussion

Page:  1 2 3 4 Next Page: Primary keys and related matters

First published by IBM developerWorks


Copyright 2004-2017 GrindingGears.com. All rights reserved.
Article copyright and all rights retained by the author.