Peter Eisentraut <peter_e@gmx.net> writes:
> 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".
Perhaps a reasonable compromise would be to divide the material into 3
chapters instead of 2 --- beginner, intermediate, advanced. Looking
at the existing TOC:
2. 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.
regards, tom lane
