Peter Eisentraut wrote:
Jeroen Ruigrok/asmodai wrote:
Because foreign keys are part of database design 101?
Indeed, but the subject matter of chapter 2 of the tutorial is more like
introduction to databases 099. Others may rightfully claim that
transactions and views are also elementary parts of database
application designs, but then there wouldn't be any advanced subjects
left.
Triggers, rules, name spaces...
Foreign keys IMHO should be in a small chapter "About database design" or "Making sure your data is valid"
or something.
I feel that there is a very useful dividing line between chapters 2 and
3: chapter 2 is about getting the data in and out, to give beginners a
feeling that the database system is working, chapter 3 is about
refining the data structures for higher convenience, maintainability,
and integrity -- "design".
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd@commandprompt.com - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org
