|
|
|
|
| LEADER |
02139nmm a2200469 u 4500 |
| 001 |
EB001916395 |
| 003 |
EBX01000000000000001079297 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 020 |
|
|
|a 9781449330200
|
| 020 |
|
|
|a 9781449330217
|
| 020 |
|
|
|a 1449330207
|
| 020 |
|
|
|a 1449328016
|
| 020 |
|
|
|a 1449330215
|
| 050 |
|
4 |
|a QA76.9.D3
|
| 100 |
1 |
|
|a Date, C. J.
|
| 245 |
0 |
0 |
|a Database design and relational theory
|b normals forms and all that jazz
|c C.J. Date
|
| 260 |
|
|
|a Sebastopol, Calif.
|b O'Reilly Media
|c 2012
|
| 300 |
|
|
|a xiii, 260 pages
|b illustrations
|
| 505 |
0 |
|
|a Includes bibliographical references and index
|
| 505 |
0 |
|
|a Part I. Setting the scene -- part II. Functional dependencies, Boyce/Codd normal form, and related matters -- part III. Join dependencies, fifth normal form, and related matters -- part IV. Orthogonality -- part V. Redundancy
|
| 653 |
|
|
|a Computers and IT. / ukslc
|
| 653 |
|
|
|a Databases / thema
|
| 653 |
|
|
|a COMPUTERS / Programming Languages / SQL. / bisacsh
|
| 653 |
|
|
|a Database design & theory / thema
|
| 653 |
|
|
|a Relational databases / Design and construction
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 490 |
0 |
|
|a Theory in practice
|
| 776 |
|
|
|z 9781449330200
|
| 776 |
|
|
|z 9781449330217
|
| 776 |
|
|
|z 1449330215
|
| 776 |
|
|
|z 9781449330187
|
| 776 |
|
|
|z 1449328016
|
| 776 |
|
|
|z 9781449328016
|
| 776 |
|
|
|z 1449330207
|
| 776 |
|
|
|z 1449330185
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781449330187/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 745.4
|
| 082 |
0 |
|
|a 005.756
|
| 520 |
|
|
|a "What makes this book different from others on database design? Many resources on design practice do little to explain the underlying theory, and books on design theory are aimed primarily at theoreticians. In this book, renowned expert Chris Date bridges the gap by introducing design theory in ways practitioners can understand - drawing on lessons learned over four decades of experience to demonstrate why proper database design is so critical in the first place."--Publisher's website
|