Hi, I started using mm.mysql-2.0.x on our test system and I noticed a difference in the behaviour of ResuletSet between this version and some older version we used.
Apparently, the older version automatically goes to the first record if you call ResultSet.getString() or similar methods. without first calling Resultset.next(). The new version however does not do this any more but throws an Exception instead. So if you forgot to call ResultSet.next() before actually retrieving the first record, everything worked in the old version, but the new version throws the exception... Has anybody noticed this so far? I know that the problem is really caused by me not calling ResultSet.next(), I was just wondering if anyone knows if there is an easier way to fix this problem than going through all my old code again. Maybe this change was not even intended by the author of the library... MARK --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
