This section contains general details (independent of the DBMS used), such as the name, application, comment, version, version extraction query, etc.
This section MUST be included if you want to work with versions at database level.
General format:
[Database]
app_name = MyApplication
app_comment = This is my database for test
database = MYBASE
version = 2.2
checkversion = SELECT MAX(VERSION) FROM APP.VERSION
Parameter |
Type |
Mandat. |
Default |
Description |
General settings |
||||
UserUtil |
string |
no |
Used to impose a default connection profile if the profile is not specified in the tool's settings. |
|
PasswordUtil |
string |
no |
Used to impose the default user profile password. |
|
Other parameters |
||||
app_name |
string |
no |
|
Application name. |
app_comment |
string |
no |
|
General comment. |
database |
string |
no |
|
Database name. |
version |
num |
yes* |
0.0 |
Database version to which the file refers. Information used to control database coherence when utilities start running and for the automatic update procedure. Numeric: (15,9) maximum. |
checkversion |
string |
yes* ** |
|
SQL query used to read the version number of an existing database. With a Btrieve database, version management is made via the creation of a "Version.ini" file in the Btrieve file directory. |
vendordll |
string |
yes* ** |
|
User DLL allowing a precise control of version management. * replaces the query specified via CheckVersion |
substitution |
num |
no |
1 |
Enables automatic substitution of the escape sequences {dbt xxx} in the queries in SQL scripts. |
| * | Mandatory for version management |
| ** | Mutually exclusive |