Closed firebird-automations closed 18 years ago
firebird-automations
commented
18 years ago Commented by: Alice F. Bird (firebirds)
Date: 2005-03-30 11:08 Sender: martijntonies Logged In: YES user_id=203974
Perhaps it's useful to change the current message to something along the lines of "input parameter mismatch" and create a new "output parameter mismatch"? That would give the user a better hint of what's going on.
firebird-automations
commented
18 years ago Commented by: Alice F. Bird (firebirds)
Date: 2005-03-26 15:13 Sender: dimitr Logged In: YES user_id=61270
Are you worried about the major error code (wrong BLR blah-blah) or about the minor one (parameter mismatch) too? I've fixed the code to return the same error as you see in DSQL with wrong number of input parameters. Now (current HEAD) it looks like:
Dynamic SQL Error. parameter mismatch for procedure P.
for input mismatches in both DSQL and PSQL, as well as for output mismatches in PSQL, including the missing RETURNING clause. Is it okay or a new error message is strongly required?
firebird-automations
commented
16 years ago
Submitted by: Martijn Tonies (martijntonies)
SFID: 1168951# Submitted By: martijntonies
Hi there,
When using a stored procedure with output parameters in a trigger or another procedure and forgetting the RETURNING_VALUES clause, a very weird error message is raised about BLR errors and the like.
Can this be modified into an error message that actually means something?
-- Martijn