Stored Code Debugger
|Previous Index Next How To Use|
Database Workbench comes with a powerful Stored Code Debugger tool. You can reach this tool by using the context menu in the Database Navigator on any Stored Procedure or Trigger and selecting Debug Procedure or Debug Trigger. Alternatively, use the Debug buttons in the object editors.
Read the generic topic on the debugger first.
Firebird does not have any debugging-hooks inside the engine. Therefore, in order to debug a stored procedure, Database Workbench emulates what is happening on the server. This makes it possible to "debug" a procedure that hasn't even been compiled into the database. The debugger has undergone serious testing and research - however errors still are possible. If you think you have found an error, don't hesitate to report it.
Parameters & Variables
In this window, you will see the current value of any parameters and variables used in the procedure. These values will be updated after each statement. The debugger will pick up "variables" from the variable declaration section.
Testing procedure results
By using the SQL button on the toolbar, you can start an SQL Editor that uses the same transaction as the debugger. With this SQL Editor, you can test your procedure result (eg: INSERTs or DELETEs) before COMMITting or ROLLING back the transaction.