Re: SQL Stored Procedure ROW_COUNT

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 05/17/2016
10:33:56 AM:

As Rob suggested, move the second GET DIAGNOSTIC to after the first.
Or better IMO:

Consider, instead of doing two separate GET DIAGNOSTIC requests for
the one DELETE statement, issue just one, immediately following the
DELETE statement; e.g.:

Cannot combine ROW_COUNT with GET CURRENT CONDITION. Results in
the following error message.

MSG ID SEV RECORD TEXT
SQL0104 30 132 Position 55 Token ROW_COUNT was not valid.

Is it really necessary to include all of the following text; all of
which will be included in the archives? Please consider adding the
signature delimiter somewhere before the corporate gibberish.

I understand you're complaining about my signature, but I don't
know what "signature delimiter" means.

Sincerely,

Dave Clark
int.ext: 91078
direct: (937) 531-6378

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331



*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************