Hello,
"SET MAXERRORCOUNT xx" seems to have no effect in loadercli input file
(Used Maxdb version : 7.5)
Could somebody tell me if this is a known bug or if I incorrectly use an
option ?
Here is the sample script that I call with loadercli (without the option
-E) :
//Folowing command should be to allow to drop myProc without stopping on
error (but it has no effect !)
SET MAXERRORCOUNT 100
//
DROP DBPROC mySample
//Folowing command is then to force to stop at first error
SET MAXERRORCOUNT 1
//
CREATE DBPROC mySample AS
BEGIN
SELECT * FROM domain.dbprocedures;
END;
//
CALL mySample
//
The script produces following report that mentions the SET MAXERRORCOUNT
100 is successfull but it has no effect because it stops at the first
encountered error. It does not when I use the option -E 100 with loadercli.
SET MAXERRORCOUNT 100
Successfully executed
DROP DBPROC mySample
Error during execution
-->-25010
SQL error -4016 = Unknown procedure name:MYSAMPLE (error position:
13[line: 1, col: 13])
Defined maximum number of errors (1) reached
Thank you for your help.
Joel
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
