You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by rw...@intermediate.de on 2004/03/16 17:54:14 UTC
Problem after update to OJB 1.0 RC 5
Hello all,
we use OJB as persistence layer and really like it! But after updating
from 0.9.8 to 1.0 RC 5 we get the exception below from the database driver
when we do a query.
We first did send it to sapdb folks as we updated the driver too (we want
to provide the jdbc 3.0 features to the ojb layer).
The answer from sapdb points to ojb, please see below ......
Best regards,
Rüdiger
----- Weitergeleitet von Rüdiger Weiss/Intermediate am 16.03.2004 17:48
-----
"Schroeder, Alexander" <al...@sap.com>
16.03.2004 16:58
An: "'rweiss@intermediate.de'" <rw...@intermediate.de>, maxdb@lists.mysql.com
Kopie:
Thema: RE: Problem after updating JDBC driver to JDBC 3.0
Hello Rüdiger,
there is no row number 0 in a result set, as row numbers start with 1
in result sets. Your application seemed wanting to navigate to the row
0.
Regards
Alexander Schröder
SAP DB, SAP Labs Berlin
> -----Original Message-----
> From: rweiss@intermediate.de [mailto:rweiss@intermediate.de]
> Sent: Tuesday, March 16, 2004 4:51 PM
> To: maxdb@lists.mysql.com
> Subject: Problem after updating JDBC driver to JDBC 3.0
>
>
> Hi all,
>
> we use apache ojb as persistence layer in our application.
>
> Querying our data we retrieve the exception below after updating
> the jdbc driver to the following version:
>
>
> Manifest-Version: 1.0
> Created-By: Apache Ant 1.5
> Main-Class: com.sap.dbtech.jdbc.DriverSapDB
>
> Name: com/sap/dbtech/jdbc/
> Specification-Title: Java Platform API Specification
> Specification-Version: 1.3.0
> Specification-Vendor: Sun Microsystems, Inc.
> Implementation-Title: SAP DB JDBC Driver
> Implementation-Version: 7.4.4 Build 003-000-002-502
> Implementation-Vendor: SAP AG
>
> Name: com/sap/dbtech/jdbcext/JDBCRowSetSapDB.class
> Java-Bean: True
>
>
>
> SQL State: 21000
>
> com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: nullInvalid
> argument
> value "row" = 0.
> at
> com.sap.dbtech.jdbc.ResultSetSapDB.absolute(ResultSetSapDB.java:236)
> at
> org.apache.ojb.broker.accesslayer.RsIterator.absolute(RsIterat
> or.java:685)
> at
> org.apache.ojb.broker.accesslayer.PagingIterator.<init>(Paging
> Iterator.java:111)
> at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.getIteratorFr
> omQuery(PersistenceBrokerImpl.java:1118)
> at
> org.apache.ojb.broker.core.QueryReferenceBroker.getCollectionB
> yQuery(QueryReferenceBroker.java:144)
> at
> org.apache.ojb.broker.core.QueryReferenceBroker.getCollectionB
> yQuery(QueryReferenceBroker.java:244)
> at
> org.apache.ojb.broker.core.QueryReferenceBroker.getCollectionB
> yQuery(QueryReferenceBroker.java:263)
> at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.getCollection
> ByQuery(PersistenceBrokerImpl.java:997)
>
>
> Any idea, when and why this happens?
>
> Best regards,
>
> Rüdiger
>
> --
> MaxDB Discussion Mailing List
> For list archives: http://lists.mysql.com/maxdb
> To unsubscribe:
http://lists.mysql.com/maxdb?unsub=alexander.schroeder@sap.com
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org