Hi Kevin,
I found, that in jdbc before 2.0 the resultset-iterator is initally positioned
before the first element in the resultset.
So the first action you have to do after you have got the resultset is to
invoke one ResultSet.next() to position your
Cursor-Iterator on the first element of the resultset. If there are no
elements in the resultset or any other error
occours you get an 'false' as an result of this first invocation of
ResultSet.next().
Perhaps this information helps .
Greeting
Claus
Kevin K Moore wrote:
Does anyone know if there is some sort of equivalent in jdbc 1.2 to jdbc
2.0's ResultSet.first()?
I'm working on an applet and it seems the VM won't support
ResultSet.first() nor ResultSet.relative(). I was wondering if there was a
work around for ResultSet.first() without actually just requerying the db?
Thanks
Kevin Moore
To unsubscribe, send a message to the address shown in the
List-Unsubscribe header of this message. If you cannot see it,
e-mail java...@lists.mysql.com instead.