×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 05/17/2016
03:04:32 PM:
... getting error: Keyword BEGIN not expected. Valid tokens: :.
What is the correct syntax? I've
Found my answer in the archives. Needed a comma-separated list
for the conditions being handled. Now I'm getting errors on my SIGNAL
statements later on in the stored procedure. If you have a global
condition handler, how do you raise an exception for the handler to take
care of? I know that if an SQL statement causes an exception or a warning
then the handler will get invoked. But, for errors that I detect via my
own testing, how do I invoke the same global handler? I thought I would
do it as follows but these are being rejected. So, what is the correct
solution? Thanks.
SET ERRCODE = '88W01';
SIGNAL SQLEXCEPTION;
Sincerely,
Dave Clark
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
