You could add triggers, rules into advanced features... You could also break joins up so that when2. The SQL Language 2.1. Introduction 2.2. Concepts 2.3. Creating a New Table 2.4. Populating a Table With Rows 2.5. Querying a Table 2.6. Joins Between Tables 2.7. Aggregate Functions 2.8. Updates 2.9. Deletions 3. Advanced Features 3.1. Introduction 3.2. Views 3.3. Foreign Keys 3.4. Transactions 3.5. Inheritance 3.6. Conclusion
I'd be inclined to put aggregates, transactions, foreign keys, and views into the "intermediate" category, leaving only inheritance as "advanced". (Or maybe we should just drop inheritance from the tutorial.) You could possibly even argue that joins are intermediate instead of basic, although that's stretching it a bit.
I agree with Peter's point that the first thing to teach is how to get data in and out.
talking about outer, left etc... it goes into advanced but basic "join on" or natural joins are in
intermediate.
J
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
-- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - [EMAIL PROTECTED] - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL
---------------------------(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