Hello

At 20/01/2003 09:24 +0100, Schroeder, Alexander wrote:
>Hi Sven,
>
>you are right. I will fix this in the next release.
>
>Regards
>Alexander Schröder
>SAP Labs Berlin
>
>> -----Original Message-----
>> From: Sven Köhler [mailto:[EMAIL PROTECTED]]
>> Sent: Sunday, January 19, 2003 7:46 PM
>> To: [EMAIL PROTECTED]
>> Subject: [BUG?] JDBC: ResultSet.relative(n)
>> 
>> 
>> Hi,
>> 
>> If a ResultSet has just been returned from the 
>> executeQuery()-methode, 
>> calling relative(n) with n>1 and even with n=1 causes a
>> "com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: 
>> Result set is positioned before first row."
>> 
>> As the javadoc of ResultSet state, the case n=1 should be 
>> identical to 
>> calling the next() method. But it isn't. It throws the above 
>> Exception, 
>> which isn't thrown, when i call next();
>> 
>> I don't think, that calling relative(n) with n>1 should fail either.
>> 
>> Thx
>>    Sven


Read again the specification, the text says that relative must throw SQLException if 
there are not current row, and this is the situation before you call next.

Regards
Blas Rodriguez Somoza


_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to