Subject isql bug (FB1.5 Final)
Author Ian A. Newby
Hi folks,
I've been moving some of our tools to FB 1.5 and have found a bug
in isql. I use the line

isql -x -o newddl.sql database.fdb -user user -password password

in a batch file to extract a development database into a script.

What I have noticed is the following:

Stored procedures with both input and output parameters are
extracted wrong. An example:

This is the create procedure for an SP_TOKENIZER in the script:

CREATE PROCEDURE SP_TOKENIZER (ORIGINALSTRING VARCHAR(20480)
CHARACTER SET NONE,
TOKENS VARCHAR(30) CHARACTER SET NONE)
AS
BEGIN EXIT; END ^

However, the alter statement in the same script is as follows:
ALTER PROCEDURE SP_TOKENIZER (ORIGINALSTRING VARCHAR(20480)
CHARACTER SET NONE,
TOKENS VARCHAR(30) CHARACTER SET NONE)
RETURNS (TOKEN VARCHAR(1024) CHARACTER SET NONE)
AS



declare variable COUNTER integer;
declare variable START integer;
declare variable FINISH integer;
declare variable CURRENTCHAR char(1);
declare variable WHITESPACE char(1);
begin
...
end ^

It seems that the create statements are not being created correctly.
This means that any stored procedures which are altered before this
one will fail if they depend on it. This all worked correctly in
1.02.

I've checked the rest of the script and it only seems to create the
returns clause if there are no input parameters.

Regards
Ian Newby