> But the problem is: the default terminator of SQL commands is ";".

Correct.

> And when creating triggers/procedures, it is needed to use ";" for
> internal commands and other terminator for "CREATE XXX ... END"
> command.

Correct.

> Then, how can I run a script with a code like this?

Your application has to take into account the terminator specified in the
script (the SET TERM command), use this terminator to extract the statements
(complete CREATE ... END blocks that can span multiple lines and contain
semicolons but without the current terminator, ^ in your case), submit that
command to the engine, proceed to the next statement.

That is exactly the task that the example on the wiki does.

But now I am confused. I understood that you have extended that example to
handle comments, buffer end, etc. Right? If yes, what had happened to the
processCommand method?

Roman