Databases supported by DBMaster
DBMaster is designed to work with virtually any relational database. Drivers and dialects are stored externally and can be added dynamically.
Vendor | Database | Versions |
Microsoft | SQL Server | 2005+ |
Oracle | MySQL | 5.1+ |
How to add a new database
Drivers are configured in file [dbmaster_home]/data/drivers.ini. It is necessary to restart dbmaster in order for modifications to be reloaded.
Property | Description |
driver.[driver_key].name | This name will be displayed to user in driver selection combobox. |
driver.[driver_key].enabled | Possible values for this parameter are true and false. When value is false driver will not be available for users. |
driver.[driver_key].class | Full qualified java class name of jdbc driver. |
driver.[driver_key].url_format | This is a help string displayed for users for connection url. |
driver.[driver_key].dialect | DBMaster will try to find a groovy script in file data\dialects\[dialect].groovy. Multiple drivers can refer to the same dialect. For example Microsoft, ODBC, and JTD drivers can refer to sqlserver dialect. |
driver.[driver_key].property.[property_key].key | Key will bed displayed to user and used in database driver. |
driver.[driver_key].property.[property_key].value | Optional 'default' value of the property. Can be overwritten by user. |
driver.[driver_key].property.[property_key].description | User-friendly description to help user to define property value. |
Sample driver definition
driver.mssql2008.name=Microsoft SQL Server
driver.mssql2008.enabled=true
driver.mssql2008.class=com.microsoft.sqlserver.jdbc.SQLServerDriver
driver.mssql2008.url_format=jdbc:sqlserver://[serverName][\instanceName][:port1433]
driver.mssql2008.dialect=sqlserver
driver.mssql2008.property.encryption.method.key=EncryptionMethod
driver.mssql2008.property.encryption.method.value=noEncryption
driver.mssql2008.property.encryption.method.description=Determines whether SSL encryption is used to encrypt data...
Implementing a dialect
Dialects for DBMaster are defined with Groovy language.
A dialect must extend abstract com.branegy.dbmaster.connection.JDBCDialect
class
and define all methods for communicating with database.