Toad World® Forums

Editor drops label prior to BEGIN - results in build error


#1

Hi,
There is a serious error with the current beta where the editor drops any label prior to a BEGIN statement. Take the following stored procedure in toad 4.6::

CREATE or replace PROCEDURE “PXX”.“PXXDLSTESTTJE” (
INOUT “IN1” INTEGER,
OUT “RETKOD” CHARACTER(22),
OUT “RETTEXT” CHARACTER(50),
OUT “RETSQLSTATE” CHARACTER(5),
OUT “RETSQLERRM” VARCHAR(500) )
SPECIFIC “PXXDLSTESTTJE”
LANGUAGE SQL
NOT DETERMINISTIC
COMMIT ON RETURN NO
EXTERNAL ACTION
MODIFIES SQL DATA
CALLED ON NULL INPUT
INHERIT SPECIAL REGISTERS
OLD SAVEPOINT LEVEL
P1: BEGIN
declare a integer default 0;
declare c char(2);
update T20 set c20 = 500;
set retkod = ‘000’;

END P1;

In the current beta this comes up as:

CREATE or replace PROCEDURE “PXX”.“PXXDLSTESTTJE” (
INOUT “IN1” INTEGER,
OUT “RETKOD” CHARACTER(22),
OUT “RETTEXT” CHARACTER(50),
OUT “RETSQLSTATE” CHARACTER(5),
OUT “RETSQLERRM” VARCHAR(500) )
SPECIFIC “PXXDLSTESTTJE”
LANGUAGE SQL
NOT DETERMINISTIC
EXTERNAL ACTION
MODIFIES SQL DATA
OLD SAVEPOINT LEVEL
BEGIN
declare a integer default 0;
declare c char(2);
update T20 set c20 = 500;
set retkod = ‘000’;

END P1;

Note the missing P1: before the begin verb. This causes a build failure.

We see this as a serious error and should be fixad for the next drop.

Regards,

John.


#2

Thanks for the information again.
We are working on a fix for this as well.
The fix will not be in the next 4.7.0.475 beta but should be in a subsequent drop.
Jeff


#3

Message from: john.enevoldson_671

Hi, Dissapointed to see that issue this is not fixed in the latest drop. Without
this fix we cannot evaluate or test the beta for stored procedure development.
Regards, John.


Historical Messages

Author: john.enevoldson_671
Date: Sun Aug 15 23:10:08 PDT 2010
Hi, Dissapointed to see that issue this is not fixed in the latest drop. Without
this fix we cannot evaluate or test the beta for stored procedure development.
Regards, John.
__

Author: jeff.podlasek
Date: Fri Jul 23 08:33:14 PDT 2010
Thanks for the information again. We are working on a fix for this as well. The
fix will not be in the next 4.7.0.475 beta but should be in a subsequent drop.
Jeff
__

Author: john.enevoldson_671
Date: Thu Jul 22 00:37:41 PDT 2010
Hi, There is a serious error with the current beta where the editor drops any
label prior to a BEGIN statement. Take the following stored procedure in toad
4.6:: CREATE or replace PROCEDURE “PXX”.“PXXDLSTESTTJE” ( INOUT “IN1” INTEGER,
OUT “RETKOD” CHARACTER(22), OUT “RETTEXT” CHARACTER(50), OUT “RETSQLSTATE”
CHARACTER(5), OUT “RETSQLERRM” VARCHAR(500) ) SPECIFIC “PXXDLSTESTTJE” LANGUAGE
SQL NOT DETERMINISTIC COMMIT ON RETURN NO EXTERNAL ACTION MODIFIES SQL DATA
CALLED ON NULL INPUT INHERIT SPECIAL REGISTERS OLD SAVEPOINT LEVEL P1: BEGIN
declare a integer default 0; declare c char(2); update T20 set c20 = 500; set
retkod = ‘000’; END P1; In the current beta this comes up as: CREATE or replace
PROCEDURE “PXX”.“PXXDLSTESTTJE” ( INOUT “IN1” INTEGER, OUT “RETKOD”
CHARACTER(22), OUT “RETTEXT” CHARACTER(50), OUT “RETSQLSTATE” CHARACTER(5), OUT
“RETSQLERRM” VARCHAR(500) ) SPECIFIC “PXXDLSTESTTJE” LANGUAGE SQL NOT
DETERMINISTIC EXTERNAL ACTION MODIFIES SQL DATA OLD SAVEPOINT LEVEL BEGIN
declare a integer default 0; declare c char(2); update T20 set c20 = 500; set
retkod = ‘000’; END P1; Note the missing P1: before the begin verb. This causes
a build failure. We see this as a serious error and should be fixad for the next
drop. Regards, John.
__



#4

Hi,
Dissapointed to see that issue this is not fixed in the latest drop. Without this fix we cannot evaluate or test the beta for stored procedure development.
Regards,
John.


#5

Message from: Helene

John,

Sorry about that. The fix for this issue actually had two parts and the second
part missed the build date for the last Beta by a couple of days. The fix is
currently complete in our code base and should definitely be out in the next
Beta drop.


Historical Messages

Author: Helene T. Rantz
Date: Mon Aug 16 06:28:38 PDT 2010

John,

Sorry about that. The fix for this issue actually had two parts and the second
part missed the build date for the last Beta by a couple of days. The fix is
currently complete in our code base and should definitely be out in the next
Beta drop.

__

Author: john.enevoldson_671
Date: Sun Aug 15 23:10:08 PDT 2010
Hi, Dissapointed to see that issue this is not fixed in the latest drop. Without
this fix we cannot evaluate or test the beta for stored procedure development.
Regards, John.
__

Author: john.enevoldson_671
Date: Sun Aug 15 23:10:08 PDT 2010
Message from: john.enevoldson_671 Hi, Dissapointed to see that issue this is not
fixed in the latest drop. Without this fix we cannot evaluate or test the beta
for stored procedure development. Regards, John.
_______________________________________ Historical Messages Author:
john.enevoldson_671 Date: Sun Aug 15 23:10:08 PDT 2010 Hi, Dissapointed to see
that issue this is not fixed in the latest drop. Without this fix we cannot
evaluate or test the beta for stored procedure development. Regards, John. __
Author: jeff.podlasek Date: Fri Jul 23 08:33:14 PDT 2010 Thanks for the
information again. We are working on a fix for this as well. The fix will not be
in the next 4.7.0.475 beta but should be in a subsequent drop. Jeff __ Author:
john.enevoldson_671 Date: Thu Jul 22 00:37:41 PDT 2010 Hi, There is a serious
error with the current beta where the editor drops any label prior to a BEGIN
statement. Take the following stored procedure in toad 4.6:: CREATE or replace
PROCEDURE “PXX”.“PXXDLSTESTTJE” ( INOUT “IN1” INTEGER, OUT “RETKOD”
CHARACTER(22), OUT “RETTEXT” CHARACTER(50), OUT “RETSQLSTATE” CHARACTER(5), OUT
“RETSQLERRM” VARCHAR(500) ) SPECIFIC “PXXDLSTESTTJE” LANGUAGE SQL NOT
DETERMINISTIC COMMIT ON RETURN NO EXTERNAL ACTION MODIFIES SQL DATA CALLED ON
NULL INPUT INHERIT SPECIAL REGISTERS OLD SAVEPOINT LEVEL P1: BEGIN declare a
integer default 0; declare c char(2); update T20 set c20 = 500; set retkod =
‘000’; END P1; In the current beta this comes up as: CREATE or replace PROCEDURE
“PXX”.“PXXDLSTESTTJE” ( INOUT “IN1” INTEGER, OUT “RETKOD” CHARACTER(22), OUT
“RETTEXT” CHARACTER(50), OUT “RETSQLSTATE” CHARACTER(5), OUT “RETSQLERRM”
VARCHAR(500) ) SPECIFIC “PXXDLSTESTTJE” LANGUAGE SQL NOT DETERMINISTIC EXTERNAL
ACTION MODIFIES SQL DATA OLD SAVEPOINT LEVEL BEGIN declare a integer default 0;
declare c char(2); update T20 set c20 = 500; set retkod = ‘000’; END P1; Note
the missing P1: before the begin verb. This causes a build failure. We see this
as a serious error and should be fixad for the next drop. Regards, John. __


__

Author: jeff.podlasek
Date: Fri Jul 23 08:33:14 PDT 2010
Thanks for the information again. We are working on a fix for this as well. The
fix will not be in the next 4.7.0.475 beta but should be in a subsequent drop.
Jeff
__

Author: john.enevoldson_671
Date: Thu Jul 22 00:37:41 PDT 2010
Hi, There is a serious error with the current beta where the editor drops any
label prior to a BEGIN statement. Take the following stored procedure in toad
4.6:: CREATE or replace PROCEDURE “PXX”.“PXXDLSTESTTJE” ( INOUT “IN1” INTEGER,
OUT “RETKOD” CHARACTER(22), OUT “RETTEXT” CHARACTER(50), OUT “RETSQLSTATE”
CHARACTER(5), OUT “RETSQLERRM” VARCHAR(500) ) SPECIFIC “PXXDLSTESTTJE” LANGUAGE
SQL NOT DETERMINISTIC COMMIT ON RETURN NO EXTERNAL ACTION MODIFIES SQL DATA
CALLED ON NULL INPUT INHERIT SPECIAL REGISTERS OLD SAVEPOINT LEVEL P1: BEGIN
declare a integer default 0; declare c char(2); update T20 set c20 = 500; set
retkod = ‘000’; END P1; In the current beta this comes up as: CREATE or replace
PROCEDURE “PXX”.“PXXDLSTESTTJE” ( INOUT “IN1” INTEGER, OUT “RETKOD”
CHARACTER(22), OUT “RETTEXT” CHARACTER(50), OUT “RETSQLSTATE” CHARACTER(5), OUT
“RETSQLERRM” VARCHAR(500) ) SPECIFIC “PXXDLSTESTTJE” LANGUAGE SQL NOT
DETERMINISTIC EXTERNAL ACTION MODIFIES SQL DATA OLD SAVEPOINT LEVEL BEGIN
declare a integer default 0; declare c char(2); update T20 set c20 = 500; set
retkod = ‘000’; END P1; Note the missing P1: before the begin verb. This causes
a build failure. We see this as a serious error and should be fixad for the next
drop. Regards, John.
__



#6

John,

Sorry about that. The fix for this issue actually had two parts and the second part missed the build date for the last Beta by a couple of days. The fix is currently complete in our code base and should definitely be out in the next Beta drop.