CREATE PROCEDURE fails in TIBCScript

[upscene]

Hi,

I just got a report saying that CREATE PROCEDURE fails in a script if SET TERM is not used. As you know, InterBase 2009 and up don't use this anymore, so TIBCScript should be able to leave this out as well.

Here's the code that fails:

CREATE PROCEDURE COUNTRY_GET_LIST_ALL
( IP_ISACTIVE Char(1) )
RETURNS
( OP_CODE VarChar(3),
OP_NAME VarChar(40),
OP_ISACTIVE Char(1)
)
AS
DECLARE VARIABLE EXCLUDE_ACTIVE CHAR(1);
BEGIN
EXCLUDE_ACTIVE = ' ';
IF (:IP_ISACTIVE = 'Y') THEN EXCLUDE_ACTIVE = 'N';
IF (:IP_ISACTIVE = 'N') THEN EXCLUDE_ACTIVE = 'Y';
FOR SELECT CODE, NAME, ISACTIVE
FROM COUNTRY
WHERE ISACTIVE :EXCLUDE_ACTIVE
INTO :OP_CODE, :OP_NAME, :OP_ISACTIVE
DO
SUSPEND;
END;

The part sent to the server is:

> CREATE PROCEDURE COUNTRY_GET_LIST_ALL
> ( IP_ISACTIVE Char(1) )
> RETURNS
> ( OP_CODE VarChar(3),
> OP_NAME VarChar(40),
> OP_ISACTIVE Char(1)
> )
> AS
> DECLARE VARIABLE EXCLUDE_ACTIVE CHAR(1)

< ERROR:

Dynamic SQL Error
SQL error code = -104
Unexpected end of command

Can you check on this?

[AndreyZ]

Hello,

The point is that the TIBCScript component uses the ";" string by default as a delimiter string that separates script statements. To solve the problem you should set the TIBCScript.Delimiter property to another string, for example, "/".

[upscene]

Hello,

The point is that the TIBCScript component uses the ";" string by default as a delimiter string that separates script statements. To solve the problem you should set the TIBCScript.Delimiter property to another string, for example, "/".

This would mean that TIBCScript does NOT work the same as InterBase 7 ISQL.

My users expect this to work.

[Dimon]

Thank you for information. We have reproduced this problem and fixed it. This fix will be included in the next IBDAC build.

[upscene]

Thank you for information. We have reproduced this problem and fixed it. This fix will be included in the next IBDAC build.

I think you can EXECUTE BLOCK to it as well, this statement has the default terminator in it too.

And obviously the TRIGGER statements too.

[AndreyZ]

Thank you for the information. We have fixed this problem for all cases mentioned above.