SUMMARY

SEARCH

Disclaimer: Authors have full rights over their works. Reproduction of any part of the content is prohibited without prior authorization.

BOOK TWO STYLES OF DATABASE DEVELOPMENT

SUMMARY

Introduction and Intended Audience
A story about table aliases, a vision about an inferior skill, how to drink wine mixed with water in France!
Writing correctly is critical for the quality of our software
A basic terminology
All types of software developers!
The same styles of development were used for many years in the user interface and in the database!
The application developer – the main target of this book
Database developers and students in IT universities are especially targeted too
The two sections of the book
Chapter 1 The concept of style
The style of development is dynamic. We need to recognize it first!
The most common styles of programming
The database development starts with the table design
Do we already start the development?
Are we ready for SQL?
Chapter 2 SQL - the beauty and the beast!
How can a query language be so important for a style of development?
What is SQL? What is not SQL?
What about programming? Is there such a thing like database programming?
Programming is a practical activity!
Should we write in the database in a certain way?
The SQL shop metaphor!
An example of bad practice!
Chapter 3 The holistic vision against the data
The concept of data set
The holistic approach versus the atomic approach – an introduction
A different model –does this model deserve to be promoted indeed?
Performance and portability - two advantages for the holistic approach.
Visual development versus SQL development
Chapter 4 What to choose: the data set or the data row?
Choosing the level of detail: the set versus the row!
Performance is poor. Performance completely blocked in any tentative of improvement.
Database programming means query, query and query all the time!
Let’s go back to the SQL shop! One more time, please!
The use of scalar functions –a typical accessory for the atomic approach!
Debugging is so simple! The code is much simpler and readable!
What is a database developer nowadays?
It’s practice time!
Chapter 5 Data transfer paradigm, the first set of examples
The exercises, the context, the goals, ways to illustrate the two approaches!
Holistic versus atomic: incrementally update a target
Chapter 6 Others atomic features used in excess
The use of scalar functions – a challenge to the set-based approach
A simple query!
Chapter 7 Writing SQL versus writing procedurally, other holistic methods
Writing SQL versus writing procedurally, another impediment!
An example of update!
Writing SQL versus writing procedurally: the power of union in the holistic approach!
Embedded SQL versus dynamic SQL – another dilemma!
Others holistic solutions: the temporary table, explicit or implicit like with a clause
Chapter 8 Row triggers. When should we follow the atomic way? Some final reflections and thoughts!
The use of row triggers: another common atomic solution used in excess
The atomic approach should be used, whenever is necessary!
Some final reflections and thoughts
The concept of SQL template
Writing horizontally or vertically: a decision to be taken!
The specific software application should be implemented holistically
The SQL itself can be better and better!
Performance, oh performance! This book is for you!
A specific data migration software application can be written in pure SQL more often than you expect!