Commented by: @luronumen

This issue is also reproducible for Stored procedures headers/bodies statements (See lines 4 and 13 from DDL_PROCEDURE.SQL file attached).

Commented by: @AlexPeshkoff

One question - what harm in extra commits?

Commented by: @luronumen

Hi Alexander

There is no harm in having an extra COMMIT, but there is also no reason for an extra COMMIT.
It was precisely because there was no reason for the existence of this extra commit, knowing that the fix is not something that requires so much work time, because of the very low risk of the side effect of the fix and knowing that the Firebird development team values quality. of DBMS that I decided to open this issue.

Best Regards,
Luciano

Commented by: @asfernandes

I didn't looked in details, but that extra commit may be due to things your script does not use (for example, computed expressions).

So it may not be a matter of just remove it, but conditionally put it only when necessary.

Commented by: @luronumen

Hi Adriano,

Thank you very much for your quick response!

The best way to find out where this extra commit comes from is to inspect the ISQL.exe code.

As you can see in the issue description it is a very simple issue to be reproducible:
1- Create a database
2- Create a procedure or function
3- Extract the database metadata using isql.exe

I believe that this issue comes with the code for creating the procedures/functions metadata because when extracting the metadata from a database without structure, this issue is not reproducible.

Best Regards,
Luciano