Skip to content
Library Home
Start Over
Research Databases
E-Journals
Course Reserves
Library Home
Login to library account
English
Deutsch
Español
Français
Italiano
日本語
Nederlands
Português
Português (Brasil)
中文(简体)
中文(繁體)
Türkçe
עברית
Gaeilge
Cymraeg
Ελληνικά
Català
Euskara
Русский
Čeština
Suomi
Svenska
polski
Dansk
slovenščina
اللغة العربية
বাংলা
Galego
Tiếng Việt
Hrvatski
हिंदी
Հայերէն
Українська
Language
Library Catalog
All Fields
Title
Author
Subject
Call Number
ISBN/ISSN
Find
Advanced Search
|
Browse
|
Search Tips
Joe Celko's SQL Programming St...
Cite this
Text this
Email this
Print
Export Record
Export to RefWorks
Export to EndNoteWeb
Export to EndNote
Save to List
Permanent link
Joe Celko's SQL Programming Style.
Annotation
Saved in:
Bibliographic Details
Main Author:
Celko, Joe
(Author)
Format:
eBook
Language:
English
Published:
San Diego : Los Angeles :
Academic Press [Imprint] Elsevier Science & Technology Books Sony Electronics [distributor]
Jan. 2009
Series:
Morgan Kaufmann Ser. in Data Management Systems Ser.
Subjects:
SQL (Computer program language)
Query languages (Computer science)
Online Access:
Click for online access
Holdings
Description
Table of Contents
Similar Items
Staff View
Table of Contents:
Front cover; Title page; Copyright page; Table of contents; front matter; Introduction; 1.1 Purpose of the Book; 1.2 Acknowledgments; 1.3 Corrections, Comments, and Future Editions; First chapter; 1. Names and Data Elements; 1.1 Names; 1.1.1 Watch the Length of Names; 1.1.2 Avoid All Special Characters in Names; 1.1.3 Avoid Quoted Identifiers; 1.1.4 Enforce Capitalization Rules to Avoid Case- Sensitivity Problems; 1.2 Follow the ISO-11179 Standards Naming Conventions; 1.2.1 ISO-11179 for SQL; 1.2.2 Levels of Abstraction; 1.2.3 Avoid Descriptive Prefixes; 1.2.4 Develop Standardized Postfixes.
1.2.5 Table and View Names Should Be Industry Standards, Collective, Class, or Plural Nouns1.2.6 Correlation Names Follow the Same Rules as Other Names ... Almost; 1.2.7 Relationship Table Names Should Be Common Descriptive Terms; 1.2.8 Metadata Schema Access Objects Can Have Names That Include Structure Information; 1.3 Problems in Naming Data Elements; 1.3.1 Avoid Vague Names; 1.3.2 Avoid Names That Change from Place to Place; 1.3.3 Do Not Use Proprietary Exposed Physical Locators; 2. Fonts, Punctuation, and Spacing; 2.1 Typography and Code.
2.1.1 Use Only Upper- and Lowercase Letters, Digits, and Underscores for Names2.1.2 Lowercase Scalars Such as Column Names, Parameters, and Variables; 2.1.3 Capitalize Schema Object Names; 2.1.4 Uppercase the Reserved Words; 2.1.5 Avoid the Use of CamelCase; 2.2 Word Spacing; 2.3 Follow Normal Punctuation Rules; 2.4 Use Full Reserved Words; 2.5 Avoid Proprietary Reserved Words if a Standard Keyword Is Available in Your SQL Product; 2.6 Avoid Proprietary Statements if a Standard Statement Is Available; 2.7 Rivers and Vertical Spacing; 2.8 Indentation; 2.9 Use Line Spacing to Group Statements.
3. Data Declaration Language3.1 Put the Default in the Right Place; 3.2 The Default Value Should Be the Same Data Type as the Column; 3.3 Do Not Use Proprietary Data Types; 3.4 Place the PRIMARY KEY Declaration at the Start of the CREATE TABLE Statement; 3.5 Order the Columns in a Logical Sequence and Cluster Them in Logical Groups; 3.6 Indent Referential Constraints and Actions under the Data Type; 3.7 Give Constraints Names in the Production Code; 3.8 Put CHECK() Constraint Near what they Check; 3.8.1 Consider Range Constraints for Numeric Values.
3.8.2 Consider LIKE and SIMILAR TO Constraints for Character Values3.8.3 Remember That Temporal Values Have Duration; 3.8.4 REAL and FLOAT Data Types Should Be Avoided; 3.9 Put Multiple Column Constraints as Near to Both Columns as Possible; 3.10 Put Table-Level CHECK() Constraints at the End of the Table Declaration; 3.11 Use CREATE ASSERTION for Multi-table Constraints; 3.12 Keep CHECK() Constraints Single Purposed; 3.13 Every Table Must Have a Key to Be a Table; 3.13.1 Auto-Numbers Are Not Relational Keys; 3.13.2 Files Are Not Tables; 3.13.3 Look for the Properties of a Good Key.
Similar Items
SQL : practical guide for developers
by: Donahoo, Michael J.
Published: (2005)
Netezza SQL
by: Coffing, Tom
Published: (2014)
SQL Server 2022 Query performance tuning : troubleshoot and optimize Query performance
by: Fritchey, Grant
Published: (2022)
Joe Celko's SQL for smarties : advanced SQL programming
by: Celko, Joe
Published: (2014)
Joe Celko's SQL for smarties : advanced SQL programming
by: Celko, Joe
Published: (2005)