The Definitive Guide to SQLiteApress, 6 déc. 2006 - 440 pages When I first began coding SQLite in the spring of 2000, I never imagined that it would be so enthusiastically received by the programming community. Today, there are millions and millions of copies of SQLite running unnoticed inside computers and gadgets made by hundreds of companies from around the world. You have probably used SQLite before without realizing it. SQLite might be inside your new cell phone or MP3 player or in the set-top box from your cable company. At least one copy of SQLite is probably found on your home computer; it comes built in on Apple’s Mac OS X and on most versions of Linux, and it gets added to Windows when you install any of dozens of third-party software titles. SQLite backs many websites thanks in part to its inclusion in the PHP5 programming language. And SQLite is also known to be used in aircraft avionics, modeling and simulation programs, industrial controllers, smart cards, decision-support packages, and medical information systems. Since there are no reporting requirements on the use of SQLite, there are without doubt countless other deployments that are unknown to me. Much credit for the popularity of SQLite belongs to Michael Owens. Mike’s articles on SQLite in The Linux Journal (June 2003) and in The C/C++ Users Journal (March 2004) int- duced SQLite to countless programmers. The traffic at the SQLite website jumped noticeably after each of these articles appeared. |
Table des matières
Introducing SQLite | 1 |
CHAPTER | 2 |
CHAPTER | 4 |
CHAPTER | 5 |
CHAPTER | 7 |
CHAPTER | 9 |
Getting Started | 17 |
The Relational Model | 47 |
Prepared Queries | 214 |
Errors and the Unexpected | 229 |
The Extension C API | 255 |
Aggregates | 278 |
Summary | 299 |
Language Extensions | 301 |
Python | 310 |
SQLite Internals | 341 |
SQL | 73 |
Querying the Database | 82 |
Modifying Data | 123 |
Transactions | 147 |
Database Administration | 153 |
Summary | 169 |
Design and Concepts | 171 |
The Core C API | 205 |
The Compiler | 355 |
Summary | 362 |
APPENDIX A SQL Reference | 365 |
APPENDIX B C API Reference | 395 |
423 | |
425 | |
Autres éditions - Tout afficher
Expressions et termes fréquents
aggregate allows application argument associated attribute base BEGIN binary callback called changes chapter char clause collation column command common compiled complete connection constraint contains COUNT create CREATE TABLE database default defined DELETE domain episodes error example execute expression extension Figure Finally food_types foods function given GROUP handle illustrates implemented important INSERT integer join language LIMIT lock logical means mode modify normal NULL objects operations output parameters performed pragma primary key produces projection provides query records referred relational model represented requires result rows rules schema SELECT session shared simply single specific SQLite statement step storage class stored string structure takes things transaction trigger true tuples type_id unique UPDATE users Windows write
Fréquemment cités
Page 431 - ... 9. Logical data independence. Application programs and terminal activities remain logically unimpaired when information-preserving changes of any kind that theoretically permit unimpairment are made to the base tables.
Page 431 - Rule 7: High-Level Insert, Update, and Delete The capability of handling a base relation or a derived relation as a single operand applies not only to the retrieval of data but also to the insertion, update and deletion of data.
Page 431 - Rule 10: Integrity Independence Integrity constraints specific to a particular relational database must be definable in the relational data sublanguage and storable in the catalog, not in the application programs.