Re: call my_proc(); or begin my_proc(); end;
- From: Mohamed Houri <mohamed.houri@xxxxxxxxx>
- To: Dominic Brooks <dombrooks@xxxxxxxxxxx>
- Date: Mon, 7 Apr 2014 12:56:41 +0200
Dominic
Thanks for your answer.
I am aware of this call which doesn't through an exception. In the case I
have mentioned in my blog article, we finally canceled the proposed
solution because of that possible exception not raised when using a call.
Best regards
Mohamed
2014-04-07 12:20 GMT+02:00 Dominic Brooks <dombrooks@xxxxxxxxxxx>:
> Sent prematurely AND with an error in my test.
>
> A scheduler prog using CALL can potentially suffer from the same problem I
> described if the prog raises a no_data_found or other exception which is
> normal / expected by SQL.
>
> CALL job will succeed.
> BEGIN END will fail with exception.
>
>
> Cheers,
> Dominic
>
> Sent from my iPhone
>
> On 7 Apr 2014, at 11:14, "Dominic Brooks" <dombrooks@xxxxxxxxxxx> wrote:
>
> >> What do you think?
> >> Do you see any issues with using a call my_proc();
> >> instead of begin my_proc(); end;
> >
> > For scheduled jobs, I don't see an issue.
> >
> > But I have seen an issue in JDBC once where the call to a stored proc
> > was missing a wrapping set of {}
> > This meant that the call to sp was translated to CALL rather than being
> wrapped with BEGIN ... END;
> > As a result, a no_data_found exception was swallowed.
> >
>
--
Bien Respectueusement
Mohamed Houri
Other related posts:
