|
|
|
|
|
|
|
|
|
|
- Overview
- How to?
- Testing an HFSQL Client/Server connection
- Mode 1: Starting the project and debugging the next connections to the database
- Mode 2: Debugging the next connections to the database coming from a specific user for a specific application
- Mode 3: Debugging an existing connection
Debugging a connection to an HFSQL server
 Available only with this kind of connection
The stored procedures and the triggers are debugged from the environment, with real execution on the server. It is possible to: - run the test of a stored procedure: by itself from the editor (see Stored procedure).
- connect the debugger onto an existing connection to trace a problem in real time.
This last case will be presented in this help page. Testing an HFSQL Client/Server connection To test an HFSQL Client/Server connection: - Open the desired project in the editor.
- Display the analysis linked to the project: click
 in the quick access buttons. - On the "Project" tab, in the "Test mode" group, expand "Test mode" and select "Debug on an HFSQL server".
- In the screen that is displayed, select:
- the user identified on the server for debugging.
- the mode for running the test and the debugger.
Three start modes are available: - Starting the project and debugging the next connections to the database.
- Debugging the next connections to the database coming from a specific user for a specific application.
- Debugging an existing connection.
Mode 1: Starting the project and debugging the next connections to the database This option is used to: - start the current project (without the debugger),
- debug the stored procedures and the triggers used from the project on a database. The elements deployed on the server are run.
To use this debug mode: - The port used for debugging is port 27281 by default. This port must be opened if a firewall is used. Indeed, the communication between the development computer and the end-user computer is done via socket. This port can be modified in the HFConf.INI file.
- The user who handles the database must have the rights to debug the database.
Remarks: Mode 2: Debugging the next connections to the database coming from a specific user for a specific application This option allows you to debug the stored procedures and the triggers used from any connection that complies with the filter criteria. If the filter criteria are not restrictive enough, there may be too many calls to the debugger. The elements deployed on the server are run. To use this debug mode: - The port used for debugging is port 27281 by default. This port must be opened if a firewall is used. Indeed, the communication between the development computer and the end-user computer is done via socket. This port can be modified in the HFConf.INI file.
- The user who handles the database must have:
- the rights to debug the database,
- the rights to debug any connection.
Remark: InTestMode returns False. Mode 3: Debugging an existing connection This option allows you to debug the stored procedures and the triggers used from an existing connection. The elements deployed on the server are run. To use this debug mode: - The port used for debugging is port 27281 by default. This port must be opened if a firewall is used. Indeed, the communication between the development computer and the end-user computer is done via socket. This port can be modified in the HFConf.INI file.
- The user who handles the database must have:
- the rights to debug the database,
- the rights to debug any connection.
Remark: InTestMode returns False.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|