Table of Contents
Parameters that are explained in this section are placed in database vendor configuration files (in build/conf/<dbVendorName>Conf.xml files and also in dbmanager.jar file as part of ‘org.enhydra.dods.conf’ package).
This parameters tune-up DODS to work with distinct database vendors and jdbc drivers, and all parameters are not appropriate for all vendors and drivers.
Some of this parameter can also be set in application *.conf file, in that case they override values defined in vendor configuration file.
To set some of database vendor specific parameters you simply go to appropriate build/conf/<dbVendorName>Conf.xml file and set value to tag:
<paramName>paramValue</paramName>
To set some of driver specific parameters you need to follow some syntax rules:
<Drivers> <fullClassNameOfJDBCDriver> <ParamName>ParamValue</ParamName> ... </fullClassNameOfJDBCDriver> … … <fullClassNameOfJDBCDriver> <ParamName>ParamValue</ParamName> ... < /fullClassNameOfJDBCDriver> ... … </Drivers>
Example:
<Drivers> <com.microsoft.jdbc.sqlserver.SQLServerDriver> <UseCursorName>false</UseCursorName> <OrderedResultSet>withPrefix</OrderedResultSet> </com.microsoft.jdbc.sqlserver.SQLServerDriver> </Drivers>
Parameter are set on jdbc driver level (can be distinct for distinct driver on same database engine).
Possible values: true, false
Default value: true
File: dbVendorConf.xml
Context: Drivers
When turned on, allow DODS to use named cursors, this is default value. Some jdbc compliant drivers, like Microsoft JDBC driver (msjdbc), don't implement this feature and need to disable it (set parameter to false) to avoid runtime Exceptions.
This parameter can also be set in app.conf file see UseCorsorName section in Chapter 22.