
JDBC Drivers Tested with Allora
|
|
Product: |
Allora, HiT JDBC/DB2, HiT JDBC/400 |
|
Version: |
All |
|
Category: |
Product Compatibility |
|
Last Updated: Topic ID: |
KBFAQ 1288 |
|
Summary: |
JDBC Drivers Tested with Allora |
The following JDBC
drivers have been tested with Allora. If you encounter problems when using
Allora
with a JDBC driver that is not listed here, contact technical support at xml-support@hitsw.com.
Database
|
Drivers
|
Issues
|
|
|
|
·
Can
be used in conjunction with an ODBC driver for access to databases when a
JDBC driver is not available. Check
the JDBC-ODBC
Bridge Documentation for more information. |
|
|
|
|
|
|
|
·
Known issue with inserting data in longvarchar or longvarbinary
fields with greater than 10
KB of data (tested with JDBC driver version 6.2). |
|
DB2 UDB |
HiT
JDBC/DB2 hit.db2.Db2Driver |
·
Does
not return table relations. |
|
DB2 UDB for iSeries (formerly AS/400) |
HiT JDBC/400 hit.as400.As400Driver |
|
|
IBM Toolbox for
Java com.ibm.as400.access.AS400JDBCDriver |
|
|
|
Sun JDBC-ODBC
bridge + HiT ODBC/400 |
|
|
Gupta SQL Base
|
jdbc.gupta.sqlbase.SqlbaseDriver |
· Identity fields not currently supported. · Binary data type not supported · Primary keys and foreign keys are not created when creating a table from Allora. |
|
ca.edbc.jdbc.EdbcDriver |
|
|
com.informix.jdbc.IfxDriver |
·
Data types not supported: interval, row, list,
set, multi-set. |
|
com.borland.datastore.jdbc.DataStoreDriver |
·
Object data type not supported. |
|
|
com.matisse.sql.MtDriver |
·
Supports
only one-to-one relations |
|
MSAccess |
Sun JDBC-ODBC
bridge + Microsoft Access Driver |
·
Table
relations not visible in Mapper due to limitation
in JDBC-ODBC bridge. |
|
MySQL |
MM.MySQL JDBC Driver for MySQL org.gjt.mm.mysql.Driver MySQL-AB JDBC Driver com.mysql.jdbc.Driver |
|
|
Oracle |
Oracle JDBC/OCI
Driver oracle.jdbc.driver.OracleDriver |
·
Problem
using NCHAR, NVARCHAR2 |
|
Oracle Thin JDBC
Driver |
·
Problem
using NCHAR, NVARCHAR2 ·
Problem
using BLOB datatype |
|
|
Sun JDBC-ODBC
bridge + Oracle ODBC Driver |
·
Problem
using NCHAR, NVARCHAR2 ·
|
|
|
BEA WebLogic jDriver(tm) for
Oracle weblogic.jdbc.oci.Driver |
·
Set the
allowMixedCaseMetaData=true in the url ·
BLOB
& CLOB not supported |
|
|
Pointbase |
Pointbase JDBC Driver com.pointbase.jdbc.jdbcUniversalDriver |
|
|
POSTGRESQL |
POSTGRESQL JDBC
Driver org.postgresql.Driver |
|
|
|
solid.jdbc.SolidDriver |
|
|
SQL Server |
BEA WebLogic jDriver(tm) for MSSQLServer weblogic.jdbc.mssqlserver4.Driver |
|
|
Opta2000 i-net JDBC driver for SQL Server com.inet.tds.TdsDriver |
|
|
|
MS SQLServer JDBC Driver com.microsoft.jdbc.sqlserver.SQLServerDriver |
Error retrieving (marshal) “real not null”
value the resultSet.getFloat returns the exception
“Value can not be converted to requested type”. If the data type is “real”
the error doesn’t happened. ·
The dataType hitns:GUID can be unmarshaled but the marshal returns always null. |
|
|
Sun JDBC-ODBC
bridge + SQL Server ODBC driver |
·
Problem
getting unicity during marshalling (Connection is
busy with results for another hstmt). This error
happens when running a marshal and showSchema is
set to true. This doesn’t happen with the JDBC driver |
|
|
Sybase ASE (Adaptive Server Enterprise) |
Sybase jConnect for JDBC |
·
Problem
if using Identity fields. The driver doesn’t return the Identity datatype. |
|
Sun JDBC-ODBC
bridge + Sybase ASE ODBC driver |
|
|
|
iAnywhere SQL Anywhere Studio |
Sybase jConnect for JDBC |
|
|
Teradata |
TeraJDBC: Teradata Driver for the JDBC Interface.
Version 03.03.00.00 com.ncr.teradata.TeraDriver |
|
|
TimesTen |
TimesTen JDBC Support com.timesten.jdbc.TimesTenDriver |
|
|
TimesTen ODBC Driver |
|
|
|
|
|
·
In the Database
Type field of the DSN configuration, we recommend "Visual Foxpro Database (.DBC)” ·
Index
and Database relationships cannot be viewed in the Mapper. ·
Auto-increment
columns not supported ·
In the
Database Type field of the DSN configuration, if you choose “Free Table
Directory”: 1.
In the
"Unmarshal Settings" dialog "Create
table path" field, set the same path as the one used in the DSN.
Otherwise the table can't be found after creation. 2.
Table
and column names can only be 10 characters long. |