| 000 | 01391nam a2200229Ia 4500 | ||
|---|---|---|---|
| 005 | 20250730165044.0 | ||
| 008 | 250728s9999 xx 000 0 und d | ||
| 020 | _a978-0-12-374730-3 | ||
| 082 | _aC 005.756 H24r | ||
| 100 | _aHarrington, Jan L. | ||
| 245 | 0 | _aRelational database design and implementation: clearly explained | |
| 250 | _a3rd ed. | ||
| 260 | _aBurlington | ||
| 260 | _b Elsevier | ||
| 260 | _c2009 | ||
| 300 | _axix, 420 p. ; ill ; 24cm | ||
| 300 | _bIncludes bibliographical references and index | ||
| 520 | _aMy favorite opening line for the database courses 1 teach is Probably the most misun-derstood term in all of business computing is database, followed closely by the word relational. At that point, some students look a bit smug because they are absolutely, positively sure that they know what a database is and that they also know what is means for a database to be relational. Unfortunately, the popular press, with the help of some PC software developers, long ago distorted the meaning of both terms, which led many businesses to think that designing a database is a task that could be left to any clerical worker who had taken a one-week course on using database software. As you will see throughout this book, however, nothing could be further from the truth. | ||
| 650 | _aDatabase design | ||
| 650 | _aRelational databases | ||
| 942 |
_2ddc _cBK |
||
| 999 |
_c236 _d236 |
||