The ::DEBUG_BREAKS table holds information about all break points defined for the current debugger session.
Field Name |
Field Type |
Field Size |
Description |
break_name |
CiChar |
43 |
Name of the break point. The value in this column may be null. |
user_id |
Integer |
4 |
Non-zero if the break point should only apply to the specific user. The value in this column may be null. |
query_id |
Integer |
4 |
Non-zero if the break point should only apply to the specific query handle. The value in this column may be null. |
object_id |
Integer |
4 |
Non-zero if the break point is set for an object in the database. Otherwise the break point if for the base script. |
Offset |
Integer |
4 |
Location in the source script where the break point is set. |
ObjectType |
Short |
2 |
Non-zero if the object_id is non-zero. Identifies the type of the object in the database. Possible values are ADS_DD_FUNCTION_OBJECT, ADS_DD_PROCEDURE_OBJECT or ADS_DD_TRIGGER_OBJECT. These constants are defined in the header file ace.h. |
When an SQL script is executed in debug mode, the ::DEBUG_BREAKS table is consulted by the query engine to determine whether execution should be suspended. If a break point matching the current executing script is found, the execution is suspended and the ::DEBUG_CONNECTIONS table is updated.
See DEBUG BREAK POINT statement for additional information.