book

Joe Celko's SQL Programming Style

by Joe Celko

May 2005

Beginner to intermediate

272 pages

5h 5m

English

Morgan Kaufmann

Read now

Unlock full access

1.1 Purpose of the Book1.2 Acknowledgments1.3 Corrections, Comments, and Future Editions
1.1 Names1.2 Follow the ISO-11179 Standards Naming Conventions1.3 Problems in Naming Data Elements
2.1 Typography and Code2.2 Word Spacing2.3 Follow Normal Punctuation Rules2.4 Use Full Reserved Words2.5 Avoid Proprietary Reserved Words if a Standard Keyword Is Available in Your SQL Product2.6 Avoid Proprietary Statements if a Standard Statement Is Available2.7 Rivers and Vertical Spacing2.8 Indentation2.9 Use Line Spacing to Group Statements
3.1 Put the Default in the Right Place3.2 The Default Value Should Be the Same Data Type as the Column3.3 Do Not Use Proprietary Data Types3.4 Place the PRIMARY KEY Declaration at the Start of the CREATE TABLE Statement3.5 Order the Columns in a Logical Sequence and Cluster Them in Logical Groups3.6 Indent Referential Constraints and Actions under the Data Type3.7 Give Constraints Names in the Production Code3.8 Put CHECK() Constraint Near what they Check3.9 Put Multiple Column Constraints as Near to Both Columns as Possible3.10 Put Table-Level CHECK() Constraints at the End of the Table Declaration3.11 Use CREATE ASSERTION for Multi-table Constraints3.12 Keep CHECK() Constraints Single Purposed3.13 Every Table Must Have a Key to Be a Table3.14 Do Not Split Attributes3.15 Do Not Use Object-Oriented Design for an RDBMS
4.1 Measurement Theory4.2 Types of Scales4.3 Using Scales4.4 Scale Conversion4.5 Derived Units4.6 Punctuation and Standard Units4.7 General Guidelines for Using Scales in a Database

5.1 Bad Encoding Schemes5.2 Encoding Scheme Types5.3 General Guidelines for Designing Encoding Schemes5.4 Multiple Character Sets
6.1 Pick Standard Constructions over Proprietary Constructions6.2 Pick Compact Constructions over Longer Equivalents6.3 Use Comments6.4 Avoid Optimizer Hints6.5 Avoid Triggers in Favor of DRI Actions6.6 Use SQL Stored Procedures6.7 Avoid User-Defined Functions and Extensions inside the Database6.8 Avoid Excessive Secondary Indexes6.9 Avoid Correlated Subqueries6.10 Avoid UNIONS6.11 Testing SQL
7.1 VIEW Naming Conventions Are the Same as Tables7.2 VIEWs Provide Row- and Column-Level Security7.3 VIEWs Ensure Efficient Access Paths7.4 VIEWs Mask Complexity from the User7.5 VIEWs Ensure Proper Data Derivation7.6 VIEWs Rename Tables and/or Columns7.7 VIEWs Enforce Complicated Integrity Constraints7.8 Updatable VIEWs7.9 Have a Reason for Each VIEW7.10 Avoid VIEW Proliferation7.11 Synchronize VIΕWs with Base Tables7.12 Improper Use of VIEWs7.13 Learn about Materialized VIEWs
8.1 Most SQL 4GLs Are Not for Applications8.2 Basic Software Engineering8.3 Use Classic Structured Programming8.4 Avoid Portability Problems8.5 Scalar versus Structured Parameters8.6 Avoid Dynamic SQL
9.1 Put the Specification into a Clear Statement9.2 Add the Words “Set of All . . ./” in Front of the Nouns9.3 Remove Active Verbs from the Problem Statement9.4 You Can Still Use Stubs9.5 Do Not Worry about Displaying the Data9.6 Your First Attempts Need Special Handling9.7 Do Not Think with Boxes and Arrows9.8 Draw Circles and Set Diagrams9.9 Learn Your Dialect9.10 Imagine That Your WHERE Clause Is “Super Ameba”9.11 Use the Newsgroups and Internet
10.1 Bad Programming in SQL and Procedural Languages10.2 Thinking of Columns as Fields10.3 Thinking in Processes, Not Declarations10.4 Thinking the Schema Should Look Like the Input Forms
Military StandardsMetadata StandardsANSI and ISO StandardsU.S. Government CodesRetail IndustryCode Formatting and Naming Conventions
Reading PsychologyProgramming Considerations