DSQL uses the JDBC protocol to communicate with databases,
which makes most major databases available. The
drivers functionalities are defined
in
dbmsdefs.sql
.
Id | Availability | Distribution | Supported Databases |
---|---|---|---|
Connector/J | v3.0.8 included in DSQL | MySQL (GPL) | MySQL |
JDBC-ODBC-Bridge | with the JRE | Sun (JDK) | Any ODBC source: SQL Server, Access, MySQL, etc. |
Free-TDS | v2.0 included in DSQL | FreeTDS.org (Open Source) | MS SQL, Sybase |
jTDS | v0.5.1 included in DSQL | SourceForge.net | MS SQL, Sybase |
MSSQL | microsoft.com | Microsoft | MS SQL, Sybase |
Note: other drivers can be added in
dbmsdefs.sql
.
The following table shows the parameters to include
in a connect
element. (also defined in
dbmsdefs.sql
)
Id | Parameters | |
---|---|---|
Connector/J | <hostname>, <port> (optional), <dbname>, <username>, <password> | |
JDBC-ODBC-Bridge | <dsn>, <username>, <password> | |
Free-TDS | <hostname>, <port> (optional), <dbname>, <username>, <password> | |
jTDS | <hostname>, <port> (optional), <dbname>, <username>, <password> | |
MSSQL | <hostname>, <port> (optional), <dbname>, <username>, <password> |
The following driver issues are automatically handled by DSQL.
Id | Issue | Resolution in DSQL |
---|---|---|
Free-TDS | does not support backward scrolling | resend the query if a request is made for a previous record |
jTDS | claims to have some scroll support, but the result sets are forward only | check that the results sets actually support backward scrolling; if not, handle as Free-TDS |
JDBC-ODBC-Bridge | requires the columns to be read in the same order as they appear in the query (only on Windows?) | check if this is the case the first time a result is read with this driver; if so cache columns as they are read |