|
|
|
|
| LEADER |
00000cam a2200000M 4500 |
| 001 |
ocn935390209 |
| 003 |
OCoLC |
| 005 |
20240623213015.0 |
| 006 |
m o d |
| 007 |
cr |n||||||||| |
| 008 |
090112e20090107mou o 000 0 eng d |
| 040 |
|
|
|a REB
|b eng
|e pn
|c REB
|d OCLCQ
|d EBLCP
|d MERUC
|d ZCU
|d ICG
|d OCLCO
|d OCLCF
|d OCLCQ
|d OCLCO
|d WYU
|d OCLCQ
|d DKC
|d OCLCQ
|d OCLCO
|d OCLCQ
|d OCLCO
|d OCLCL
|
| 019 |
|
|
|a 936903670
|
| 020 |
|
|
|a 9780080478838
|
| 020 |
|
|
|a 0080478832
|q (E-Book)
|
| 035 |
|
|
|a (OCoLC)935390209
|z (OCoLC)936903670
|
| 037 |
|
|
|b 00991439
|
| 050 |
|
4 |
|a QA76.73.S67 ǂb C433 2005eb
|
| 049 |
|
|
|a HCDD
|
| 100 |
1 |
|
|a Celko, Joe,
|e author.
|
| 245 |
1 |
0 |
|a Joe Celko's SQL Programming Style.
|
| 260 |
|
|
|b Academic Press [Imprint]
|c Jan. 2009
|a San Diego :
|b Elsevier Science & Technology Books
|a Los Angeles :
|b Sony Electronics [distributor]
|
| 300 |
|
|
|a 1 online resource
|
| 336 |
|
|
|a text
|b txt
|2 rdacontent
|
| 337 |
|
|
|a computer
|b c
|2 rdamedia
|
| 338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
| 490 |
1 |
|
|a The Morgan Kaufmann Ser. in Data Management Systems Ser.
|
| 520 |
8 |
|
|a Annotation
|b Are you an SQL programmer that, like many, came to SQL after learning and writing procedural or object-oriented code? Or have switched jobs to where a different brand of SQL is being used, or maybe even been told to learn SQL yourself? If even one answer is yes, then you need this book. A "Manual of Style" for the SQL programmer, this book is a collection of heuristics and rules, tips, and tricks that will help you improve SQL programming style and proficiency, and for formatting and writing portable, readable, maintainable SQL code. Based on many years of experience consulting in SQL shops, and gathering questions and resolving his students' SQL style issues, Joe Celko can help you become an even better SQL programmer.
|
| 505 |
0 |
|
|a 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.
|
| 505 |
8 |
|
|a 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.
|
| 505 |
8 |
|
|a 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.
|
| 505 |
8 |
|
|a 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.
|
| 505 |
8 |
|
|a 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.
|
| 650 |
|
0 |
|a SQL (Computer program language)
|
| 650 |
|
0 |
|a Query languages (Computer science)
|
| 650 |
|
7 |
|a Query languages (Computer science)
|2 fast
|
| 650 |
|
7 |
|a SQL (Computer program language)
|2 fast
|
| 758 |
|
|
|i has work:
|a Joe Celko's SQL programming style (Text)
|1 https://id.oclc.org/worldcat/entity/E39PCFv6J9jCkVmCjQ6bhtFjhb
|4 https://id.oclc.org/worldcat/ontology/hasWork
|
| 776 |
0 |
8 |
|i Print version:
|a Celko, Joe.
|t Joe Celko's SQL Programming Style.
|d Burlington : Elsevier Science, ©2014
|z 9780120887972
|
| 830 |
|
0 |
|a Morgan Kaufmann Ser. in Data Management Systems Ser.
|
| 856 |
4 |
0 |
|u https://ebookcentral.proquest.com/lib/holycrosscollege-ebooks/detail.action?docID=234986
|y Click for online access
|
| 903 |
|
|
|a EBC-AC
|
| 994 |
|
|
|a 92
|b HCD
|