Saurabh Vyas wrote:
So what you mean to say that rolling back of transaction should be
dependent on the application's behavior. If my understanding is correct,
then in DERBY-2017, the way I tried to handle the case in not correct.
How this case should be handled then?
From looking at the comments in DEBRY-2017 the question that jumps out
to me is why is the parameter being checked by the client after the
execute has occurred on the embedded driver? Seems like pushing the
check into the embedded engine might make more sense.
Dan.
