From your knowledge is there a reference book (preferably not to expensive) which will answer my sort of questions - ie the rational behind the mechanics of SQL2003 rather than just the mechanics?

Roy Lambert

Ole


As an example of the sort of things I'm interested in understanding:

Why was it decided to implement the aggregate functions such as sum or avg to ignore nulls rather than following the same behaviour as when operating on columns (ie return a null) and require the use of a WHERE field IS NOT NULL


Roy Lambert

Roy,

<< From your knowledge is there a reference book (preferably not to
expensive) which will answer my sort of questions - ie the rational behind
the mechanics of SQL2003 rather than just the mechanics? >>

The only SQL book I've read is:

SQL:1999 Understanding Relational Language Components
Jim Melton, Alan R. Simon
ISBN 1-55860-456-1

I'm not sure if it will answer your sort of questions but Jim Melton is
the editor of the ISO/IEC 9075 standard since SQL-92 (iirc) and he has first
hand knowledge about the architecture and decisions made by the development
team and later ratified by the comittee. While the book is pretty technical
and perhaps best suited as a reference to implementors of SQL (like RDBMS
vendors), Mr. Melton IMO explains standard SQL very well, including the
rationale behind some of the decisions.

Ole Willy Tuv

Ole


have a look on Amazon.co.uk - the price ranges from just over £25 to just over £147

Roy Lambert

Roy,

<< have a look on Amazon.co.uk - the price ranges from just over £25 to just
over £147 >>

Sorry, I can't help you with the cost of this piece of jewellery they
probably gone out of stock

Ole Willy Tuv