翻译文献Database Configuration.docVIP

大连交通大学2016届本科生毕业设计（论文）外文翻译  PAGE - 32 - 外文原文 Database Configuration SQLite doesn’t have a configuration file. Rather, all of its configuration parameters are implemented using pragmas. Pragmas work in different ways. Some are like variables; others are like commands. They cover many aspects of the database, such as runtime information, database schema, versioning, file format, memory use, and debugging. Some pragmas are read and set like variables, while others require arguments and are called like functions. Many pragmas have both temporary and permanent forms. Temporary forms affect only the current session for the duration of its lifetime. The permanent forms are stored in the database and affect every session. The cache size is one such example. This section covers the most commonly used pragmas. A complete list of all SQLite pragmas can be found in Appendix A. The Connection Cache Size The cache size pragmas control how many database pages a session can hold in memory. To set the default cache size for the current session, you use the cache_size pragma: sqlite PRAGMA cache_size; cache_size 2000 sqlite PRAGMA cache_size=10000; sqlite PRAGMA cache_size; cache_size 10000 You can permanently set the cache size for all sessions using the default_cache_size pragma. This setting is stored in the database. This will only take effect for sessions created after the change, not for currently active sessions. One of the uses for the cache is in storing pending changes when a session is in a RESERVED state (it has a RESERVED lock), as described earlier in the section “Transactions.” If the session fills up the cache, it will not be able to continue further modifications until it gets an EXCLUSIVE lock, which means that it may have to first wait for readers to clear. If you or your program(s) perform many updates or deletes on a database that is being used by many other sessions, it may help you to increase the cache size. The larger the cache size, the more modifications