[teiid-issues] [JBoss JIRA] Commented: (TEIID-1428) ODBC connection fails if the TeiidDriver is not registered.

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574762#comment-12574762 ] 

Steven Hawkins commented on TEIID-1428:
---------------------------------------

As long as the full client jar is in the classpath then there shouldn't be a problem as the service provider mechanism should trigger the registration.  But since odbc is dependent upon the client anyway we shouldn't need to use the drivermanager at all right?

> 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