6 Replies Latest reply on Mar 4, 2013 9:17 AM by 992449

    Modification of behaviour on executeUpdate ojdbc5



      On the project i'm working on now there is a place where an executeUpdate(request) is producing an ORA-01008 since it's using ojdbc5 (was ojdbc14 before).
      This executeUpdate was not properly use as it is done after a prepareStatement(request)/binding/executeUpdate() but without rebinf variables as the same values are used. This way to proceed is of course not the best but it was ok with ojdbc14.
      I would like to know if somebody encounter this kid of differences on other class or method in ojdb5 ?