Различия

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

--- fox-manager-2.0-bpa:1.-общая-информация:тонкие-настройки-подключения-к-базе-данных [2020/06/10 21:13] – [Список доступных настроек] erazor
+++ fox-manager-2.0-bpa:1.-общая-информация:тонкие-настройки-подключения-к-базе-данных [2023/09/06 19:27] (текущий) – [Проблемы с кодировкой] Техподдержка
@@ Строка 3: / Строка 3: @@
 По умолчанию программа Fox Manager уже настроена таким образом, чтобы максимально облегчить подключение к базе данных. Типовые настройки подходят для 95% пользователей, однако бывают ситуации, когда специфические настройки сервера или языковые настройки системы приводят к тому, что пользователи начинают испытывать проблемы с подключением или работой с базой данных.
+===== Длина текстовых колонок в БД =====
+По умолчанию текстовые строки записываются в базу данных как **varchar(255)**, что обычно соответствует 255 символам текста (кроме таких баз данных, как Oracle, где используется длина в 255 байт, а при использовании Unicode один символ может занимать до 3 байт).
+Обычно такого количества символов хватает, чтобы уместить туда названия функций, процессов, документов и др. элементов справочников программы. Но, при необходимости, вы можете изменить это значение, задав свою длину строк.
+Для этого необходимо отредактировать файл **Settings.ini**, который находится в папке **C:\Users\<имя пользователя>\AppData\Roaming\Fox Manager\**
+Измените значение параметра **DefaultStringColWidth=255** в разделе **[Settings]**.
+Для корректной работы необходимо изменить это значение для всех пользователей программы (отредактировать файлы Settings.ini в их папках). Если значение было изменено уже после того, как база данных была создана, то изменять структуру таблиц в базе данных для текстовых полей необходимо будет вручную, для соответствия заданному параметру.
+Не рекомендуем без необходимости менять это значение, а особенно, уменьшать значение ниже 255, так как это может привести к проблемам с совместимостью с будущими версиями программы.
 ===== Проблемы с кодировкой =====
-Среди таких проблем можно отдельно выделить несоответствие кодировки, используемой сервером и программой, что приводит к тому, что вместо букв отображаются специфические символы или знаки вопроса «???????».
+Иногда несоответствие кодировки, используемой сервером БД и программой, приводит к тому, что вместо букв отображаются специфические символы или знаки вопроса «???????».
-В случае возникновения подобных проблем следует прибегнуть к тонкой настройке соединения программы с базой данных. Параметры этих настроек находятся в файле **Connection.ini**, который расположен в папке: **C:\Users\<имя пользователя>\AppData\Roaming\Fox Manager 2.x BPA\**
+В случае возникновения подобных проблем следует прибегнуть к тонкой настройке соединения программы с базой данных. Параметры этих настроек находятся в файле **Connection.ini**, который расположен в папке: **C:\Users\<имя пользователя>\AppData\Roaming\Fox Manager\**
 Откройте данный файл, например, в блокноте и отредактируйте параметры настроек подключения. Обратите внимание, что для каждого типа базы данных в файле **Connection.ini** существует свой раздел. Чтобы решить проблемы с кодировкой в большинстве случае достаточно изменить значение параметра **UseUnicode** с **False** на **True**.
 {{  :fox-manager-2.0-bpa:1.-общая-информация:connection-ini.png?nolink&  }}
+===== Проблемы при одновременном доступе к базе SQLite =====
+База данных SQLite является файловой и рекомендуется для работы одного пользователя, если вы планируете активно пользовать программой одновременно с нескольких рабочих мест и держать активными сразу несколько соединений с базой данных, то рекомендуем использовать клиент-серверную базу, например, PostgreSQL, MySQL, MS SQL Server и пр. Тем не менее, база данных SQLite позволяет организовать одновременную работу нескольких пользователей, для этого достаточно выставить следующие параметры в файле **Connection.ini** для типа базы [SQLite]:
+  * BusyTimeout = 5000
+  * LockingMode = lmNormal
+  * Synchronous = smExtra
 ===== Проблемы при подключении к базе MySQL 8.x =====
@@ Строка 18: / Строка 39: @@
   * Установите в настройках сервера MySQL 8 опцию «Use Legacy Authentication Method». Иногда для этого нужно запустить установку сервера заново и выбрать «Reconfigure» на странице установки/конфигурации.
-  * Попробуйте выбрать прямой метод подключения к базу данных. Для этого отредактируйте файл Connection.ini и поставьте значение параметра Direct=True в разделе [MySQL]
+  * Попробуйте выбрать прямой метод подключения к базе данных. Для этого отредактируйте файл Connection.ini и поставьте значение параметра Direct=True в разделе [MySQL]
   * Если подключится к базе прямым методом не удаётся, установите значение параметра Direct=False в разделе [MySQL] и обновите библиотеку доступа (libmysql.dll) до той же версии, которая используется на сервере. Не забывайте, что нужно учитывать разрядность (x86 или x64).
@@ Строка 53: / Строка 74: @@
 |EnableMemos|If set to True, TMemoField and TWideMemoField will be created for BLOB subtype 1 fields. The default value is False.|
 |ForceUnloadClientLibrary|Use the option to force unloading of the client library after the connection is closed. The default value is False.|
-|IPVersion|Use the IPVersion property to specify Internet Protocol Version.\\Supported values:\\ivIPBoth (default)Specifies that either Internet Protocol Version 6 (IPv6) or Version 4 (IPv4) will be used.\\ivIPv4Specifies that Internet Protocol Version 4 (IPv4) will be used.\\ivIPv6Specifies that Internet Protocol Version 6 (IPv6) will be used.\\Note: Internet Protocol Version support has been added in Firebird 3. To use the IPVersion option, your client library version must be version 3 or higher. When the TIPVersion property is set to ivIPBoth, a connection attempt will be made via IPv6 if it is enabled on the operating system. If the connection attempt fails, a new connection attempt will be made via IPv4.|
+|IPVersion|Use the IPVersion property to specify Internet Protocol Version. Supported values: **ivIPBoth** (default) Specifies that either Internet Protocol Version 6 (IPv6) or Version 4 (IPv4) will be used. **ivIPv4** Specifies that Internet Protocol Version 4 (IPv4) will be used. **ivIPv6** Specifies that Internet Protocol Version 6 (IPv6) will be used. Note: Internet Protocol Version support has been added in Firebird 3. To use the IPVersion option, your client library version must be version 3 or higher. When the TIPVersion property is set to ivIPBoth, a connection attempt will be made via IPv6 if it is enabled on the operating system. If the connection attempt fails, a new connection attempt will be made via IPv4.|
 |NoDBTriggers|Use the option to enable or disable all database triggers. By default, all triggers are enabled.|
 |Params|The option allows to specify custom parameters of the transaction. Refer to InterBase API Guide for more information on this parameters. Custom parameters will be used only when the TUniTransaction.IsolationLevel property is set to ilCustom. Multiple parameters can be separated either with the CRLF or with the ";" character.|
@@ Строка 66: / Строка 87: @@
 |Embedded|If True, connects to Embedded MySQL server. If False, connects to MySQL server. The default value is False.|
 |EmbeddedParams|Allows to set such parameters of embedded connection as –basedir, –datadir, etc. Parameters should be separated with newline characters (#13#10), for example: //UniConnection.SpecificOptions.Values['MySQL.EmbeddedPrams'] := '–basedir=.'#13#10'–datadir=data';// \\   \\ The default value is ''|
+|HttpTrustServerCertificate|This option specifies whether or not the driver should trust the server certificate when connecting to the server. The default value is False – the driver won't trust the server certificate and will verify validity of the server certificate instead. If set to True, the driver will trust the server certificate.|
 |Interactive|Determines the inactivity timeout before the server breaks the connection. If true, the server breaks the connection after number of seconds specified in interactive_timeout sever variable, otherwise wait_timeout is used. The default value is false. The interactive_timeout and wait_timeout variables can be set in my.ini file.|
 |IPVersion|Use the IPVersion property to specify the Internet Protocol version. The default value is **ivIPv4**. **ivIPBoth** Specifies that either IPv6 or IPv4 Internet Protocol version is used. Note: when the TIPVersion property is set to ivIPBoth, there occurs an attempt to connect via IPv6 (if it is enabled in the OS); if the attempt fails - there occurs an attempt to connect via IPv4. **ivIPv4** specifies that the IPv4 Internet Protocol version is used. **ivIPv6** specifies that the IPv6 Internet Protocol version is used|
@@ Строка 115: / Строка 137: @@
 |PacketSize|Network packet size in bytes. The packet size property value must be between 512 and 32,767. The default network packet size is 4,096.|
 |PersistSecurityInfo|The data source object is allowed to persist sensitive authentication information such as password along with other authentication information.|
-|Provider|This property allows you to specify a provider from the list of supported providers or use the Direct mode. The default value of this property is prAuto. In this case a provider of the most recent version is used. Some features added to SQL Server 2005 require the SQL Native Client (prNativeClient) provider to be used. If chosen provider is not installed, an exception is raised. This property can have the following values: **prAuto** (default) The default value. If the SQL Native Client provider is found, equals to prNativeClient, otherwise equals to prSQL. **prSQL** Uses the provider preinstalled with Windows that has limited functionality. **prNativeClient** Uses the SQL Native Client. It should be installed on the computer to use this Provider value. This provider offers the maximum functionality set. **prCompact** SQL Server 2005 Compact Edition provider. **prDirect** Connect to SQL Server directly via TCP/IP.|
+|Provider|This property allows you to specify a provider from the list of supported providers or use the Direct mode. The default value of this property is prAuto. In this case a provider of the most recent version is used. Some features added to SQL Server 2005 require the SQL Native Client (prNativeClient) provider to be used. If chosen provider is not installed, an exception is raised. This property can have the following values: **prAuto** (default) The default value. If the SQL Native Client provider is found, equals to prNativeClient, otherwise equals to prSQL. **prMSOLEDB** Uses Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). You need to have the driver installed on your system to use this value for Provider. **prSQL** Uses the provider preinstalled with Windows that has limited functionality. **prNativeClient** Uses the SQL Native Client. It should be installed on the computer to use this Provider value. This provider offers the maximum functionality set. **prCompact** SQL Server 2005 Compact Edition provider. **prDirect** Connect to SQL Server directly via TCP/IP.|
 |QuotedIdentifier|Causes Microsoft® SQL Server™ to follow the SQL-92 rules regarding quotation mark delimiting identifiers and literal strings. Identifiers delimited by double quotation marks can be either Transact-SQL reserved keywords or can contain characters not usually allowed by the Transact-SQL syntax rules for identifiers. QuotedIdentifier must be True when creating or manipulating indexes on computed columns or indexed views. If QuotedIdentifier is False, CREATE, UPDATE, INSERT, and DELETE statements on tables with indexes on computed columns or indexed views will fail. **True** (default) Identifiers can be delimited by double quotation marks, and literals must be delimited by single quotation marks. All strings delimited by double quotation marks are interpreted as object identifiers. Therefore, quoted identifiers do not have to follow the Transact-SQL rules for identifiers. They can be reserved keywords and can include characters not usually allowed in Transact-SQL identifiers. Double quotation marks cannot be used to delimit literal string expressions; single quotation marks must be used to enclose literal strings. If a single quotation mark (') is a part of the literal string, it can be represented by two single quotation marks ("). QuotedIdentifier must be True when reserved keywords are used for object names in the database. **False** (BDE compatibility) Identifiers cannot be quoted and must follow all Transact-SQL rules for identifiers. Literals can be delimited by either single or double quotation marks. If a literal string is delimited by double quotation marks, the string can contain embedded single quotation marks, such as apostrophes.|
+|CompactLocaleIdentifier|Specifies the locale ID. The default value is the system default locale on Windows systems and 0 on other systems.|
+|IPVersion|Use the IPVersion property to specify Internet Protocol Version. Supported values: **ivIPBoth** Specifies that either Internet Protocol Version 6 (IPv6) or Version 4 (IPv4) will be used. **ivIPv4** (default) Specifies that Internet Protocol Version 4 (IPv4) will be used. **ivIPv6** Specifies that Internet Protocol Version 6 (IPv6) will be used. Note: When the TIPVersion property is set to ivIPBoth, a connection attempt will be made via IPv6 if it is enabled on the operating system. If the connection attempt fails, a new connection attempt will be made via IPv4.|
+|MultiSubnetFailover|Use the MultiSubnetFailover option to configure the prNativeClient or prMSOLEDB provider to faster detect and connect to the currently active server by making simultaneous connection attempts to all IP addresses associated with the group listener of a SQL Server AlwaysOn Availability Group or a SQL Server Failover Cluster Instance. The default value is False.|
+|UseWideMemos|Use the option to manage the field type that will be created for the NTEXT data type. If True (default), TWideMemo fields will be created for the NTEXT data type. If False, TMemo fields will be created.|
+|UuidWithBraces|Use the UuidWithBraces option to specify whether the values of UUID fields are returned with braces. The default value is True.|
 |TrustServerCertificate|Lets enabling traffic encryption without validation. The default value is False. This option is only supported by SQL Server 2005 with using SQL Native Client as OLE DB provider.|
 |WorkstationID|A string identifying the workstation. The default value is the name of your machine.|
@@ Строка 148: / Строка 175: @@
 |ThreadSafety|Allows to use the OCI in multi-threaded environment. The ThreadSafety option must be True before any non blocking fetch of rows or SQL statement execution takes place.|
 |UseOCI7|Use the UseOCI7 option to force TUniConnection use OCI 7 call style only. The default value is False.  |
+|EnableLargeint|When set to True, the provider maps Oracle numbers with precision more than 9 and less than 18 to TIntegerField, otherwise numbers are mapped to TFloatField. The default value is False.|
+|PrecisionSmallint|This option allows dataset to represent fields as TSmallintField if NUMBER field precision is less or equal to PrecisionLargeInt. The default value is 4.|
+|UnicodeEnvironment|Enables or disables using OCI Unicode Environment. When this option is enabled, Unicode characters can be used in SQL statements. Disable this option if you have encountered some problems with Unicode Environment.|
 |UseUnicode|Enables or disables Unicode support. Affects on character data fetched from the server. When set to True all character data is stored as WideStrings, and TStringField is replaced with TWideStringFiled. Supported starting with Oracle 8.|
@@ Строка 155: / Строка 185: @@
 |Charset|Setups the character set which will be used to transfer character data between client and server.|
 |ConnectionTimeout|The time to wait for a connection to open before raising an exception.|
-|IPVersion|Use the IPVersion property to specify the Internet Protocol version. The default value is ivIPv4. **ivIPBoth** Specifies that either IPv6 or IPv4 Internet Protocol version is used. Note: when the TIPVersion property is set to ivIPBoth, there occurs an attempt to connect via IPv6 (if it is enabled in the OS); if the attempt fails - there occurs an attempt to connect via IPv4. **ivIPv4** Specifies that the IPv4 Internet Protocol version is used. **ivIPv6** Specifies that the IPv6 Internet Protocol version is used.  |
+|HttpPassword|Use the HttpPassword option to specify the password for HTTP authorization.|
-|ProtocolVersion|Set the ProtocolVersion to pv20 to work with PostgreSQL servers 7.3 or lower that don't support the 3.0 protocol.  |
+|HttpTrustServerCertificate|This option specifies whether or not the driver should trust the server certificate when connecting to the server. The default value is False – the driver won't trust the server certificate and will verify validity of the server certificate instead. If set to True, the driver will trust the server certificate.|
+|HttpUrl|Use the HttpUrl option to specify the URL of the PHP tunneling script.|
+|HttpUsername|Use the HttpUsername option to specify the username for HTTP authorization.|
+|MessagesCharset|Specifies the character set that will be used to transfer error messages from the server to the client.|
+|IPVersion|Use the IPVersion property to specify the Internet Protocol version. The default value is ivIPv4. **ivIPBoth** Specifies that either IPv6 or IPv4 Internet Protocol version is used. Note: when the TIPVersion property is set to ivIPBoth, there occurs an attempt to connect via IPv6 (if it is enabled in the OS); if the attempt fails - there occurs an attempt to connect via IPv4. **ivIPv4** Specifies that the IPv4 Internet Protocol version is used. **ivIPv6** Specifies that the IPv6 Internet Protocol version is used.|
+|ProtocolVersion|Specifies protocol version to be used when several versions are available. Supported values: **pv20** Set ProtocolVersion to pv20 to work with PostgreSQL server version 7.3 or older that don't support protocol version 3.0. **pv30** Set ProtocolVersion to pv30 to enforce protocol version 3.0. **pvAuto** (default) Set ProtocolVersion to pvAuto to automatically select between protocol versions depending on the specific query for the best possible performance.|
+|ProxyHostname|Use the ProxyHostName option to specify the host name or IP address to connect to the proxy server.|
+|ProxyPassword|Use the ProxyPassword option to specify the password for the proxy server.|
+|ProxyPort|Use the ProxyPort option to specify the port for a TCP/IP connection with the proxy server.|
+|ProxyUsername|Use the ProxyUsername option to specify the username for the proxy server.|
 |Schema|Use the Schema property to set the search path for the connection to the specified schema. This setting offers a convenient way to perform operations on objects in a schema other than that of the current user without having to qualify the objects with the schema name.|
 |SSLCACert|The pathname to the certificate authority file.|
@@ Строка 162: / Строка 201: @@
 |SSLChipherList|The list of allowable ciphers to use for SSL encryption.|
 |SSLKey|The pathname to the key file.|
-|SSLMode|This option determines whether or with what priority an SSL connection will be negotiated with the server. If PostgreSQL is compiled without SSL support, using option smRequire will cause an error, while options smAllow and smPrefer will be accepted, but PgDAC will not in fact attempt an SSL connection.  |
+|SSLMode|This option determines whether or with what priority an SSL connection will be negotiated with the server. Supported values: **smAllow** Negotiates trying first a non-SSL connection, then if that fails, tries an SSL connection. **smDisable** (default) Only an unencrypted SSL connection will be attempted. **smPrefer** Negotiates trying first an SSL connection, then if that fails, tries a regular non-SSL connection. **smRequire** Tries only an SSL connection. **smVerifyCA** Verifies server identity by validating the server certificate chain up to the root certificate installed on the client machine. **smVerifyFull** Verifies server identity by validating the server certificate chain up to the root certificate installed on the client machine and validates that the server hostname matches the server certificate. Note: If PostgreSQL is compiled without SSL support, using option smRequire will cause an error, while options smAllow and smPrefer will be accepted, but PgDAC will not in fact attempt an SSL connection.|
+|UseHttp|The UseHttp option enables the use of HTTP tunneling to connect to the server. The default value is False.|
+|UuidWithBraces|Use the UuidWithBraces option to specify whether the values of UUID fields are returned with braces. The default value is True.|
 |UseUnicode|Enables or disables Unicode support. Affects character data fetched from the server. When set to True, all character data is stored as WideStrings, and TStringField is replaced by TWideStringFiled.|
@@ Строка 169: / Строка 210: @@
 |ASCIIDataBase|Enables or disables ASCII support. The default value is False. Note:For this option usage set the UseUnicode option to false.|
 |BusyTimeout|Use the ClientLibrary option to set or get the timeout of waiting for locked resource (database or table). If resource is not unlocked during the time specified in BusyTimeout, then SQlite returns the SQLITE_BUSY error. Default value of this option is 0.  |
+|CipherLicense|Holds a license key for SQLCipher Commercial Edition. Note that SQLCipher is not supported in the Direct mode.|
+|ConnectMode|The connection mode. **cmDefault** - The default value. The database is opened for reading and writing. Corresponds to the SQLite default behavior. **cmReadWrite** - The database is opened for reading and writing. **cmReadOnly** - The database is opened in read-only mode.|
 |ClientLibrary|Use the ClientLibrary option to set or get the client library location.|
 |DateFormat|Defines the format for storing dates in the database. If it is not specified, the default yyyy-mm-dd format will be used.  |
@@ Строка 179: / Строка 222: @@
 |ForegnKeys|Enables or disables the enforcement of foreign key constraints. Foreign key constraints are disabled by default in SQLite, so this option can be used to force enabling or disabling them by the application. Default value of this option is True.|
 |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.|
+|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.|
+|NativeDate|If the option is set to True, the date and time values will be stored in the database in the native SQLite format, and when retrieved, they will be converted to the TDateTime type. If set to False, no conversion to the TDateTime type will be made. The default value is True.|
 |ReadUncommitted|Enables or disables Read-Uncommitted isolation mode. A database connection in read-uncommitted mode does not attempt to obtain read-locks before reading from database tables as described above. This can lead to inconsistent query results if another database connection modifies a table while it is being read, but it also means that a read-transaction opened by a connection in read-uncommitted mode can neither block nor be blocked by any other connection. Default value of this option is False.  |
+|Synchronous|The database synchronization mode when writing to disk. **smOff** - The database engine continues without syncing after handing data off to the operating system. If the application running SQLite crashes, the data will safe, unless the operating system crashes or the computer loses power before data has been written to disk, in which case the database might become corrupted. This is the fastest mode. **smNormal** - The database engine still syncs at the most critical moments, but less often than in the FULL mode. The Normal mode is faster than the Full mode. When using the WAL mode (and probably the DELETE mode) with synchronous=NORMAL, data is safe from corruption. The synchronous=NORMAL setting is a reasonable choice for most applications running in the WAL mode. **smFull** - The database engine ensures that all content is safely written to disk before continuing. This preserves database integrity even in case of an operating system failure or power outage. It is a safe, but slower mode, and is most commonly used when not in the WAL mode. **smExtra** - This mode is similar to the FULL mode, but in the DELETE mode, the directory containing the rollback journal is synced after that journal is unlinked to commit a transaction. This provides additional durability if a power outage occurs right after the commit. Note: Keep the default Synchronous=smOff and LockingMode=lmExclusive for the best perfomance.|
 |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. Affects character data fetched from the server. When set to True, all character data is stored as WideStrings, and TStringField is replaced by TWideStringFiled.|
+|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.|
 \\