Commented by: @pavel-zotov

I've found that following sample still can`t be compiled:

set term ^;
create or alter procedure sp_test1 as
begin
exit;
end -- blah-blah-blah-1
^

create or alter procedure sp_test2 as
begin
exit;
end /*/* blah-blah-blah-2 *//*/* blah-blah-blah-2 */ ......... repeating these dummy comment all in single line, up-to... 100 Megabyte :-)
^

Both on 32 and 64 bit (build #⁠ 3.0.0.32008) following error is produced:

Expected end of statement, encountered EOF

Packed script please see in attach.

PS. Is this somehow relate to this ticket or to recently fixed CORE4890 ? or this completely new bug ?

Commented by: @pavel-zotov

It seems that maximal size of single SQL statement that can be successfully compiled is 10 590 614 bytes.
After that value, when size is 10 590 615 or 10 590 616 bytes, compiler raises "Single isql command exceeded maximum buffer size".
And when size is 10 590 617 bytes and more it produces "Expected end of statement, encountered EOF".

AFAIR, hard-coded limit is 10 Mb, i.e. 10 485 760. How this limit can be exeeded (see attahed "sql-command-with-huge-comment-about-compiler-implementation-limit.zip", file huge-comment-max-can-be-compiled-ok.sql with size 10590614) ?
And why different messages appear when sql statement exceeded upper bound ?

Commented by: @dyemanov

The 10MB limit does not raise any error, it just truncates the SQL string. So the error message could really be different, depending on what grammar rule is incomplete. If you don't like that, we may raise "implementation limit exceeded" instead.

Commented by: @pavel-zotov

IMHO compiler should produce only one message ("implementation limit exceeded") in any case, regardless of input string length.