Firebird Documentation Index → Firebird Vulcan Release Notes v. 1.1 → The fb_config Utility → Object Definition Syntax |
[ lacuna ]
[ lacuna ]
The actual installation directory.
The translation of the parameter RootDirectory or the installation directory if that parameter is undefined.
The current directory.
The current name
The translated value of the first wildcarded portion of the current name
The translated value of the nth wildcarded portion of the current name
The basic format of an object definition is.-
<object name> parameter value[ value&] </object>
The known objects are server, provider, SecurityManager, SecurityPlugin, gateway, and database.
<provider engine11> LockFileName $(root)/Firebird Vulcan.lck library $(root)/bin/engine11 $(root)/bin64/engine11 </provider>
[ lacuna ]
<SecurityManager SecurityDb> SecurityDatabase $(root)/security.fdb AuthAccount user AuthPassword lookup SecurityPlugin SecurityDb </SecurityManager>
Only one security plugin is supported currently.-
<SecurityPlugin SecurityDb> library $(root)/bin/securitydb $(root)/bin64/securitydb </SecurityPlugin>
A database object definition can have one of two forms. It can map a database name, possibly wild-carded, to one or more providers and apply other parameters to the database like this.-
<database *> filename $0 provider remote engine11 services </database>
The other form of the database object definition changes the name given for the database without giving it any other characteristics. When the configuration file manager finds a database object that simply renames the database, it reapplies all configuration files in order, using the new name rather than the name originally supplied.
<database yachts.lnk> filename caine:c:\harrison\metadata.fdb </database>
Unless you include at least one provider in a database object, the only parameter you can set is the database name.
Firebird Documentation Index → Firebird Vulcan Release Notes v. 1.1 → The fb_config Utility → Object Definition Syntax |