Oliver Jowett <oliver@opencloud.com> writes:
> Can you show us the application code that causes this? It may be an
> application bug that was hidden by the old driver's behaviour. Newer
> drivers tend to be more aggressive about checking resultset positioning,
> enforcing spec requirements, etc.
Never mind. I found the problem in my code, I was calling getString()
after next() returned false. Sorry for the noise.
Regards,
Manuel.