翻译文献The Connection Lifecycle.docVIP

大连交通大学2016届本科生毕业设计（论文）外文翻译  PAGE - 16 - 外文原文 The Connection Lifecycle Connections are the sole means through which to operate on a database. The connection lifecycle consists of three phases: 1. Connect to the database. Connecting involves creating a database connection object of some sort. The connection object manages transactions (through its associated pager), often performs simple one-step queries (using the wrapped query functions), and creates statement objects for prepared queries. 2. Perform transactions. As you know, all commands are executed within transactions. By default, a database connection runs in autocommit mode. This means that every SQL command it executes runs under its own independent transaction. The alternative is to manually declare transactions using BEGIN..COMMIT. In this scenario, multiple commands can run together within the same transaction. 3. Disconnect from the database. Disconnecting from a database involves closing the database file and the files of any attached databases. Other activities involved with query processing include handling errors, busy conditions, and schema changes, all of which are done through the utility functions covered in the following sections. Connecting to a Database Connecting to a database involves little more than opening a file. Every SQLite database is stored in a single operating system file—one database to one file. The function used to connect, or open, a database in the C API is sqlite3_open(), and is basically just a system call for opening a file. SQLite can also create in-memory databases. In most extensions, if you use :memory: or an empty string as the name for the database, it will create the database in RAM. The database will only be accessible to the connection that created it (it cannot be shared with other connections). Furthermore, the database will only last for the duration of the connection. It is deleted from memory when the connection closes. When you connect to a database on d