*** 81,87 **** _: For programs that have a lot of data that must be sifted and sorted in diverse ways, it is often easier and quicker to load the data into ! an in-memory SQLite database and use query with joins and ORDER BY clauses to extract the data in the form and order needed rather than to try to code the same operations manually. Using an SQL database internally in this way also gives the program --- 81,87 ---- _: For programs that have a lot of data that must be sifted and sorted in diverse ways, it is often easier and quicker to load the data into ! an in-memory SQLite database and use queries with joins and ORDER BY clauses to extract the data in the form and order needed rather than to try to code the same operations manually. Using an SQL database internally in this way also gives the program *************** *** 152,158 **** can do to prevent it. _: A good rule of thumb is that you should avoid using SQLite ! in situations where the same database will be accessed simultenously from many computers over a network filesystem. *: *High-volume Websites* --- 152,158 ---- can do to prevent it. _: A good rule of thumb is that you should avoid using SQLite ! in situations where the same database will be accessed simultaneously from many computers over a network filesystem. *: *High-volume Websites* *************** *** 170,176 **** the engine has to allocate a bitmap of dirty pages in the disk file to help it manage its rollback journal. SQLite needs 256 bytes of RAM for every 1MB of database. For smaller databases, the amount of memory ! required is not a problem, but when database begin to grow into the multi-gigabyte range, the size of the bitmap can get quite large. If you need to store and modify more than a few dozen GB of data, you should consider using a different database engine. --- 170,176 ---- the engine has to allocate a bitmap of dirty pages in the disk file to help it manage its rollback journal. SQLite needs 256 bytes of RAM for every 1MB of database. For smaller databases, the amount of memory ! required is not a problem, but when databases begin to grow into the multi-gigabyte range, the size of the bitmap can get quite large. If you need to store and modify more than a few dozen GB of data, you should consider using a different database engine. *************** *** 185,190 **** database. For many situations, this is not a problem. Each application does its database work quickly and moves on, and no lock lasts for more ! than a few dozen milliseconds. But there are some problems that require more concurrancy, and those problems will need to seek a different solution. --- 185,190 ---- database. For many situations, this is not a problem. Each application does its database work quickly and moves on, and no lock lasts for more ! than a few milliseconds. But there are some situations that require more concurrancy, and those problems will need to seek a different solution.
Small. Fast. Reliable.
Choose any three.
Choose any three.
|
|