Removal of leading whitespaces before first 'BEGIN' from SP source
------------------------------------------------------------------

                 Key: CORE-4764
                 URL: http://tracker.firebirdsql.org/browse/CORE-4764
             Project: Firebird Core
          Issue Type: Bug
    Affects Versions: 3.0 Beta 1
            Reporter: Pavel Zotov
            Priority: Trivial


This code:

set term ^;
create or alter procedure sp_test(x int, y int) returns(z bigint) as
                begin
                  z=x+y;
                  suspend;
                end
^
set term ;^
commit;
set blob all;
set list on;
select replace(replace(rdb$procedure_source,' ','.'), ascii_char(9), '.') sp_src
from rdb$procedures
where rdb$procedure_name = upper('sp_test');

-- produces:

1) on 2.1.7 and 2.5.5:
SP_SRC                          0:4
................begin
..................z=x+y;
..................suspend;
................end

2) on 2.0.7 and 3.0:
SP_SRC                          0:4
begin
..................z=x+y;
..................suspend;
................end

So, leading whitespaces that were left side of starting 'BEGIN' keyword, are 
removed in 3.0.

Is it possible to store source code without any distortion ?


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to