Subject Metadata update
Author Carlos Macao
I was trying to build an automated application install which among
other tasks tries to update DB metadata with a bunch of scripts. I
was looking for a solution which could protect all this operations
under a transaction umbrella with a unique and final commit or
rollback conditioned by the install success.

The problem has to do with compiled statements which depend on new
fresh metadata entries (like inserting a new SP which depends on a
new Table, all in the same script using only a final commit).

Is there any way to achieve that with this Firebird limitation?

Best regards,
Carlos Macao