*The most updated PostgreSQL book on the market, covering version 8.0 *Highlights the most popular PostgreSQL APIs, including C, Perl, PHP, and Java *This is two books in one; it simultaneously covers key relational database design principles, while teaching PostgreSQL

SQL in a Nutshell applies the eminently useful "Nutshell" format to Structured Query Language (SQL), the elegant--but complex--descriptive language that is used to create and manipulate large stores of data. For SQL programmers, analysts, and database administrators, the new second edition of SQL in a Nutshell is the essential date language reference for the world's top SQL database products. SQL in a Nutshell is a lean, focused, and thoroughly comprehensive reference for those who live in a deadline-driven world.This invaluable desktop quick reference drills down and documents every SQL command and how to use it in both commercial (Oracle, DB2, and Microsoft SQL Server) and open source implementations (PostgreSQL, and MySQL). It describes every command and reference and includes the command syntax (by vendor, if the syntax differs across implementations), a clear description, and practical examples that illustrate important concepts and uses. And it also explains how the leading commercial and open sources database product implement SQL. This wealth of information is packed into a succinct, comprehensive, and extraordinarily easy-to-use format that covers the SQL syntax of no less than 4 different databases.When you need fast, accurate, detailed, and up-to-date SQL information, SQL in a Nutshell, Second Edition will be the quick reference you'll reach for every time. SQL in a Nutshell is small enough to keep by your keyboard, and concise (as well as clearly organized) enough that you can look up the syntax you need quickly without having to wade through a lot of useless fluff. You won't want to work on a project involving SQL without it.

Introductory, theory-practice balanced text teaching the fundamentals of databases to advanced undergraduates or graduate students in information systems or computer science.

This new edition of an established textbook provides an introduction to the practice and principles of relational databases. It emphasises data modelling and the consequent construction of a database and reflects the importance of Structured Query Language (SQL). It contains new material on web-based databases and MySQL. There is increased coverage of the differences between Access and Oracle in SQL. Case studies and sample data feature on an accompanying web-sites.

For programmers who prefer content to frills, this guide has succinct and straightforward information for putting Access to its full, individually tailored use.

This book provides a practical and proven approach to designing relational databases. It contains two complementary design methodologies: logical data modeling and relational database design. The design methodologies are independent of product-specific implementations and have been applied to numerous relational product environments. 0201114348B04062001

Contents Should we tell you the whole story? Of course, there is an inevitable tension in trying to work like this. For example, in Chapter 16 we talk about referential integrity. There are - sentially six different flavors of referential integrity but Access only s- ports four of them (they are the most important ones however, so you aren’t missing out on too much). The problem is this. Should we tell you about the other two? If we do, as an Access user you have every right to be annoyed that we are telling you about a feature you can’t use. On the other hand, the six different types that we describe are part of the re- tional world and this book is about that world – we are not trying to teach you how to use Access, we are simply using Access to illustrate the relational model. Ultimately we decided to risk your ire and to describe all of the features of the relational model as we see it, even if Access doesn’t support all of them. One advantage of this approach is that if you need to use a different database engine you will almost certainly find the extra information useful. Incidentally, this is not meant to imply that Access is somehow lacking as a relational database engine. The reason we chose it for the first book is that it is such a good example of a relational database tool.