The following changes has
been made in the debugger of stored procedures and triggers:
Now you can
trace procedures which can handle errors. (WHEN);
Procedures
with
the POST_EVENT code have been added;
Handling of
the
BREAK command has been added;
Minor fixes
have
been made.
Now the DDLExtractor
considers view interdependency, and dependencies of triggers and
procedures on views. In previous BlazeTop builds this script operated
incorrectly.
Now the RecreateDDL for
view considers dependencies. In previous BlazeTop builds this script
worked incorrectly, because it did not take into account objects with
views.
The DDLFinder works more
rapidly for Firebird 2.1.
Now domain dependencies
also show procedures which are dependent from the domain.
Procedure and trigger
dependencies also show domains which they are dependent on.
In the DDLExtractor you
can generate a script with EXECUTE BLOCK (for Firebird 2.x). This
script operates much faster than an ordinary one. To generate a
different script you should use the UseExecuteBlock property in the
inspector. Restriction of use:
tables with BLOBs will be shown without
EXECUTE BLOCK in any case.
The code editor operates
much faster when you do Paste, Undo, Redo or Replace (previous BlazeTop
builds worked with huge texts slower).
Now in the code editor you
can change the selection mode from “by block” to
“by column” and from “by
column” to “by block” by pressing
Alt-Shift-arrow.
A parameter dialog box
has been added. If several parameters are of the same name, their value
is asked once in the parameter value box.
Now you can save the log
for selected parameters between sessions.
Bugs fixed:
The DDL text for expression indices was reported
incorrectly
(for Firebird 2.x). Fixed.
The DDL table texts with External files were shown
incorrectly. Fixed.
UDF dependencies work accurately now.
In Firebird 2.1 the SQLPlayer operated incorrectly with
objects which had comments on national languages, when it executed the
script with CREATE DATABASE. Fixed.
Sometimes the DDLExtractor worked incorrectly with float
field
values (it generated such wrong strings as 111E-308). Fixed.