Различия

Показаны различия между двумя версиями страницы.

--- fox-manager-2.0-bpa:1.-общая-информация:тонкие-настройки-подключения-к-базе-данных [2021/07/07 15:24] – erazor
+++ fox-manager-2.0-bpa:1.-общая-информация:тонкие-настройки-подключения-к-базе-данных [2021/07/07 15:24] – erazor
@@ Строка 215: / Строка 215: @@
 |ForceCreateDatabase|Used to force TLiteConnection to create a new database before opening a connection, if the database does not exist.|
-|JournalMode|The journal mode. **jmDelete** - The rollback journal is deleted at the conclusion of each transaction. **jmTruncate** - The rollback journal is stored in volatile RAM. It reduces disk I/O, but decreases database safety and integrity. If the application using SQLite crashes in the middle of a transaction, the database file may become corrupt. **jmPersist** - The rollback journal file is not deleted when the transaction is commited. The header of the journal is filled with zeroes to prevent other connections rolling back from the journal. This mode optimizes performance on platforms where deleting or truncating a file is much more expensive than overwriting the first block of a file with zeros. **jmMemory** - The rollback journal is stored in volatile RAM. This reduces the disk I/O, but decreases database safety and integrity. If the application using SQLite crashes in the middle of a transaction in this mode, the database file is likely to become corrupt. **jmWAL** - A write-ahead log is used instead of a rollback journal to implement transactions. When data database is updated, the original content is preserved in the database file and the changes are appended in a separate WAL file. All the transactions that are appended in the WAL file are eventually transferred back into the original database. **jmOff** - The rollback journal is completely disabled. No rollback journal is created, thus there is no rollback journal to delete. The ROLLBACK command does not work -- it behaves in an undefined way. Avoid using the ROLLBACK command when the journal mode is disabled. **jmDefault** - The default value. If the database was previously opened in the WAL mode, then Default will open the database in the WAL mode; otherwise, the database will be opened in the Delete mode. |
+|JournalMode|The journal mode. **jmDelete** - The rollback journal is deleted at the conclusion of each transaction. **jmTruncate** - The rollback journal is stored in volatile RAM. It reduces disk I/O, but decreases database safety and integrity. If the application using SQLite crashes in the middle of a transaction, the database file may become corrupt. **jmPersist** - The rollback journal file is not deleted when the transaction is commited. The header of the journal is filled with zeroes to prevent other connections rolling back from the journal. This mode optimizes performance on platforms where deleting or truncating a file is much more expensive than overwriting the first block of a file with zeros. **jmMemory** - The rollback journal is stored in volatile RAM. This reduces the disk I/O, but decreases database safety and integrity. If the application using SQLite crashes in the middle of a transaction in this mode, the database file is likely to become corrupt. **jmWAL** - A write-ahead log is used instead of a rollback journal to implement transactions. When data database is updated, the original content is preserved in the database file and the changes are appended in a separate WAL file. All the transactions that are appended in the WAL file are eventually transferred back into the original database. **jmOff** - The rollback journal is completely disabled. No rollback journal is created, thus there is no rollback journal to delete. The ROLLBACK command does not work – it behaves in an undefined way. Avoid using the ROLLBACK command when the journal mode is disabled. **jmDefault** - The default value. If the database was previously opened in the WAL mode, then Default will open the database in the WAL mode; otherwise, the database will be opened in the Delete mode.|
 |LockingMode|The database locking mode. **lmExclusive** - The database connection never releases file locks. The first time the database is read or written in this mode, a shared lock is obtained and held. Use this mode if you want to prevent other processes from accessing the database file, reduce the number of filesystem operations, or access WAL databases without using the shared memory. **lmNormal** - The database connection unlocks the database file at the conclusion of each read or write transaction.|
@@ Строка 226: / Строка 226: @@
 |TimeFormat|Defines the format for storing time in the database. If it is not specified, the default hh24:mi:ss format will be used.  |
 |UseUnicode|Enables or disables Unicode support. When set to True, all character data is stored as WideString, and TStringField is used instead of TWideStringField. The default value is False.|