RE: JDBC driver issue

Hi Heiko,
Have you use a java.sql.Statement or a java.sql.PreparedStatement for executing 
the query? SQL Studio uses parse/execute, so this might be the difference. I 
think the error belongs to database kernel. Could you send me a vtrace 
http://sapdb.2scale.net/moin.cgi/VTrace? 
If not possible could you send me at least a JDBC Trace 
http://sapdb.2scale.net/moin.cgi/JdbcTrace?

What is the version of your database kernel?

regards,
Marco

----------------------------------------------
Marco PASKAMP
MaxDB, SAP Labs Berlin  

>-----Original Message-----
>From: Heiko Giesselmann [mailto:heiko.giesselmann@xxxxxxxxxxxxx] 
>Sent: Donnerstag, 28. Oktober 2004 17:34
>To: maxdb@xxxxxxxxxxxxxxx
>Subject: JDBC driver issue
>
>Hi,
>
>I have a SQL statement that works fine when executed via SQL studio. 
>When I am executing the same statement via JDBC and attempt to 
>retrieve 
>result data from the ResultSet I get the following exception:
>
>Fatal Error: com.sap.dbtech.jdbc.exceptions.DatabaseException: 
>[-4000]: 
>Unknown result table at 
>com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPac
>ket.java:71) 
>at 
>com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSap
>DB.java:824) 
>at 
>com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:483) 
>at 
>com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:371) 
>at 
>com.sap.dbtech.jdbc.FetchInfo.executeFetchCommand(FetchInfo.java:244) 
>at com.sap.dbtech.jdbc.FetchInfo.executeFetchFirst(FetchInfo.java:205) 
>at 
>com.sap.dbtech.jdbc.ResultSetSapDB.fetchFirst(ResultSetSapDB.ja
>va:2449) 
>at 
>com.sap.dbtech.jdbc.ResultSetSapDB.next(ResultSetSapDB.java:367
>) at ....
>
>This is with the following driver version:
>
>Implementation-Title: MaxDB JDBC Driver
>Implementation-Version: 7.6.0   Build 000-000-003-034
>Implementation-Vendor: MySQL MaxDB
>
>The problem can be reproduced as follows:
>
>create table t1 (a integer, b integer)
>--
>create table t2 (a integer, b integer)
>--
>create view v_t2 as
>  select distinct a, b from t2
>--
>insert into t1 (a,b) values (1,2)
>--
>insert into t2 (a,b) values (1,2)
>--
>select t1.a, v_t2.a
>  from t1, v_t2
> where t1.a = v_t2.a
>
>Executing the SQL statement above via SQL Studio works fine. Executing 
>the same SQL statement via above mentioned JDBC driver will 
>result in an 
>exception. If the view is defined without 'distinct' the 
>statement works 
>fine via JDBC (but obviously with potentially different results).
>
>Any idea if this is a known bug or if there is any workaround?
>
>Thanks, Heiko
>
>------------------------------------------------------------------
>This mail has been inspected by Webwasher - a CyberGuard Company -
>leading technology for E-mail and Web Security.
>
>Webwasher - keeping your Web clean!
>------------------------------------------------------------------
>
>-- 
>MaxDB Discussion Mailing List
>For list archives: http://lists.mysql.com/maxdb
>To unsubscribe:    
>http://lists.mysql.com/maxdb?unsub=Marco.Paskamp@xxxxxxx
>
>

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx