This happens in V5 datasource. The locks are not released until the resultset is closed. As the result, this code will cause a deadlock:
Of course, one solution would be to rewrite all our functions to use the same connection, however that'd require too much time. Is there any way to force V5 datasource to behave the same way V4 did, where the locks were released as soon as select query was executed?
Also, I checked and updateable resultsets are still not supported. So that's not a solution either.
[ September 12, 2003: Message edited by: Joseph Magerramov ]