SQR Runner » Debugger

Integrated debugging allows execution of programs line-by-line and SQL result sets row-by-row.

Special features unleashing productivity yet unseen for SQR development:

• "On-the-fly" Variable Inspection
  Moving the mouse cursor over a SQR variable during debugging shows it's actual value as hint popup.
• Conditional Breakpoints
  Each breakpoint may have a condition upon which it is being stopped at.
  E.g. only stop at breakpoint if a variable has a certain value.
• Watches
  Automatic observation of user defined variables or expressions during runtime.
• Expression Evaluation
  Either shows values for variables/database columns/expressions and also offers capability to process a LET, SHOW or DISPLAY command in between.
• Runtime variable changes
  During debugging values of variables and even database columns may be changed without changing actual code.
  This may be used to to e.g. influence the program flow for IF constructs etc.
• Code-stepping / Tracing
  Tracing into procedures works across files, e.g. stepping through code inside INCLUDEs opens the corresponding file in the editor.
• Emit SQL to File
  Optionally all generated SQL definitions and actual commands sent to the database may be logged to a file.
  This includes both the core SQL declaration as well as the runtime SQL with all parameters.

Debugger restrictions:
The debugger is aimed to step/run through code but not to create actual print output files. Therefore no print output files are generated and print related commands are merely recognized and skipped during debugging sessions.
Processing of RDBMS-specific language constructs, such as PL/SQL for Oracle, is limited at this time and may cause the debugger session to stop.