![]() |
![]() |
| Paypal | FTP | CCD | Buscar | Trucos | Trabajo | Foros |
|
|||||||
| Registrarse | FAQ | Miembros | Calendario | Guía de estilo | Temas de Hoy |
|
|
Herramientas | Buscar en Tema | Desplegado |
|
#17
|
|||
|
|||
|
enlaces:
========================= http://www.sqlite.org/lockingv3.html 2.0 Overview Locking and concurrency control are handled by the pager module. The pager module is responsible for making SQLite "ACID" (Atomic, Consistent, Isolated, and Durable). The pager module makes sure changes happen all at once, that either all changes occur or none of them do, that two or more processes do not try to access the database in incompatible ways at the same time, and that once changes have been written they persist until explicitly deleted. The pager also provides a memory cache of some of the contents of the disk file. The pager is unconcerned with the details of B-Trees, text encodings, indices, and so forth. From the point of view of the pager the database consists of a single file of uniform-sized blocks. Each block is called a "page" and is usually 1024 bytes in size. The pages are numbered beginning with 1. So the first 1024 bytes of the database are called "page 1" and the second 1024 bytes are call "page 2" and so forth. All other encoding details are handled by higher layers of the library. The pager communicates with the operating system using one of several modules (Examples: os_unix.c, os_win.c) that provides a uniform abstraction for operating system services. The pager module effectively controls access for separate threads, or separate processes, or both. Throughout this document whenever the word "process" is written you may substitute the word "thread" without changing the truth of the statement. ===================================================== http://www.sqlite.org/mostdeployed.html Most Widely Deployed SQL Database We believe that there are more copies of SQLite in use around the world than any other SQL database engine, and possibly all other SQL database engines combined. We cannot be certain of this since we have no way of measuring either the number of SQLite deployments nor the number of deployments of other databases. But we believe the claim is defensible. The belief that SQLite is the most widely deployed SQL database engine stems from its use as an embedded database. Other database engines, such as MySQL, PostgreSQL, or Oracle, are typically found one to a server. And usually a single server can serve multiple users. With SQLite, on the other hand, a single user will typically have exclusive use of multiple copies of SQLite. SQLite is used on servers, but it is also used on desktop PC, and in cellphones, and PDAs, and MP3-players, and set-top boxes. Estimates At the end of 2006, there were 100 million websites on the internet. [1] Let us use that number as a proxy for the number of deployed SQL database engines other than SQLite. Not every website runs an SQL database engine and not every SQL database engine runs a website. Larger websites run multiple database engines. But the vast majority of smaller websites (the long tail) share a database engine with several other websites, if they use a database engine at all. And many large SQL database installations have nothing to do with websites. So using the number of websites as a surrogate for the number of operational SQL database engines is a crude approximation, but it is the best we have so we will go with it. (Readers are encouraged to submit better estimates.) Now let's consider where SQLite is used: 300 million copies of Mozilla Firefox. 20 million Mac computers, each of which contains multiple copies of SQLite 20 million websites run PHP which has SQLite built in. [3] We have no way of estimating what fraction of those sites actively use SQLite, but we think it is a significant fraction. 450 million registered Skype users. 20 million Symbian smartphones shipped in Q3 2007 [5] Newer versions of the SymbianOS have SQLite built in. It is unclear exactly how many Symbian phones actually contain SQLite, so we will use a single quarter's sales as a lower bound. 10 million Solaris 10 installations, all of which require SQLite in order to boot. Millions and millions of copies of McAfee anti-virus software all use SQLite internally. Millions of iPhones use SQLite Millions and millions of other cellphones from manufactures other than Symbian and Apple use SQLite. This has not been publicly acknowledged by the manufactures but it is known to the SQLite developers. There are perhaps millions of additional deployments of SQLite that the SQLite developers do not know about. By these estimates, we see at least 500 million SQLite deployments and about 100 million deployments of other SQL database engines. These estimates are obviously very rough and may be off significantly. But there is a wide margin. So the SQLite developers think it is likely that SQLite is the most widely deployed SQL database engine in the world. Si una base de datos tiene futuro es SQlite y conviene adentrarse en ellas, es SQlite3. Y no es lo que yo digo, tampoco, Don Casimiro. |
|
|
Temas Similares
|
||||
| Tema | Autor | Foro | Respuestas | Último mensaje |
| SQLITE:Establecer Contraseña a mi db | bitbow | Conexión con bases de datos | 0 | 17-09-2010 23:48:34 |
| Usuario y Contraseña??? | danytorres | Oracle | 1 | 24-07-2007 16:16:19 |
| Usuario, contraseña, rol | santiago14 | Firebird e Interbase | 1 | 11-12-2006 00:00:38 |
| Form con usuario y contraseña | nenufer | Varios | 3 | 19-05-2006 11:37:35 |
| Usuario y contraseña con ADOconnection | Gelmin | Conexión con bases de datos | 3 | 27-09-2005 08:42:48 |
|