Subject | RE: [ib-support] Re: problem with very simple Stored Procedure |
---|---|
Author | Alan McDonald |
Post date | 2002-08-27T21:40:27Z |
pain in the neck? hhmmm
well I would have make my final comment that it is not a bug in Marathon to
follow the specification for SP creation. Try some other tools to see if you
get the same error. It may, however, be a wonderful feature for new clients
to be able to guess where the end of your statement is and issue set term
statements when needed. It may even be wrapping all your statements in set
term lines. But it is not a bug sorry.
Why don't you put it on the marathon sourceforge suggestions list?
Alan
-----Original Message-----
From: duilio_fos [mailto:irel_llc@...]
Sent: Wednesday, 28 August 2002 7:07
To: ib-support@yahoogroups.com
Subject: [ib-support] Re: problem with very simple Stored Procedure
Alan,
Please follow exactly the following steps:
1. create generator NEW_ID
2. execute the following code (in Marathon SQL editor)
create procedure newid
returns (RESULT integer)
as
begin
result=GEN_ID(NEW_ID, 1);
end
3. you should get the following error message:
"ISC ERROR CODE 335544569 - ISC ERROR MESSAGE - Dynamic SQL error -
SQL Error code= -104 - unexpected end of command"
4. take the same code and paste it into the IB_SQL editor
5. the code is executed successfully and you will be able to see the
SP correctly listed by Marathon among the other SPs
6. following Helen's advice, re-write the code as:
SET TERM ^;
create procedure newid
returns (RESULT integer)
as
begin
result=GEN_ID(NEW_ID, 1);
end ^
SET TERM ; ^
7. this works ok (but it is a pain in the neck).
The "set term" command should not be necessary when the command is
given interactively.
Marathon version 15 - to say one - did not require it.
As a result, I expect the problem to be fixed in Marathon's next
build.
Best regards
Duilio
Yahoo! Groups Sponsor
ADVERTISEMENT
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
well I would have make my final comment that it is not a bug in Marathon to
follow the specification for SP creation. Try some other tools to see if you
get the same error. It may, however, be a wonderful feature for new clients
to be able to guess where the end of your statement is and issue set term
statements when needed. It may even be wrapping all your statements in set
term lines. But it is not a bug sorry.
Why don't you put it on the marathon sourceforge suggestions list?
Alan
-----Original Message-----
From: duilio_fos [mailto:irel_llc@...]
Sent: Wednesday, 28 August 2002 7:07
To: ib-support@yahoogroups.com
Subject: [ib-support] Re: problem with very simple Stored Procedure
Alan,
> version 1.6 Build 16 with IBObjects 3.4.Bsame version as the one I am using.
Please follow exactly the following steps:
1. create generator NEW_ID
2. execute the following code (in Marathon SQL editor)
create procedure newid
returns (RESULT integer)
as
begin
result=GEN_ID(NEW_ID, 1);
end
3. you should get the following error message:
"ISC ERROR CODE 335544569 - ISC ERROR MESSAGE - Dynamic SQL error -
SQL Error code= -104 - unexpected end of command"
4. take the same code and paste it into the IB_SQL editor
5. the code is executed successfully and you will be able to see the
SP correctly listed by Marathon among the other SPs
6. following Helen's advice, re-write the code as:
SET TERM ^;
create procedure newid
returns (RESULT integer)
as
begin
result=GEN_ID(NEW_ID, 1);
end ^
SET TERM ; ^
7. this works ok (but it is a pain in the neck).
The "set term" command should not be necessary when the command is
given interactively.
Marathon version 15 - to say one - did not require it.
As a result, I expect the problem to be fixed in Marathon's next
build.
Best regards
Duilio
Yahoo! Groups Sponsor
ADVERTISEMENT
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]