[
https://issues.jboss.org/browse/TEIID-1428?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-1428:
-------------------------------------
That is what I thought, but DriverManager is not loading the driver for some reason. Yes,
the client jar is in "lib" directory. The simple solution is what you are
suggesting, to directly use the TeiidDriver and void the DriverManager altogether.
What I do not understand is how it worked before?
ODBC connection fails if the TeiidDriver is not registered.
-----------------------------------------------------------
Key: TEIID-1428
URL:
https://issues.jboss.org/browse/TEIID-1428
Project: Teiid
Issue Type: Bug
Components: ODBC
Affects Versions: 7.2
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
When the ODBC connection is made to the Teiid Server, it uses the JDBC connection using
"local" mode. To make this connection it uses the DriverManager. However, if the
Teiid Driver is not already registered with the VM, then the ODBC client will see the
below error.
$iodbctest DSN=test
iODBC Demonstration program
This program shows an interactive SQL processor
Driver Manager: 03.52.0709.0909
1: SQLDriverConnect = ERROR: No suitable driver found for
jdbc:teiid:TransactionsRevisited;ApplicationName=ODBC
org.teiid.jdbc.TeiidSQLException: No suitable driver found for
jdbc:teiid:TransactionsRevisited;ApplicationName=ODBC (210) SQLSTATE=08001
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira