Debugging options:

This is list of options for debugging

These options are inside given virtual database configuration file. For example: postgresTest-vdb_1.conf. The filename depends on the name of the vdb → nameOfVdb.conf.

⚠️ Note: You can use SHIFT with mouse scroll to scroll horizontally!

Key	Requirements	Conf File field	Description	Possible values	Default
Pass-through Enabled	Access Mode = JDBC	loggingEnabled	When in JDBC mode, the system can be set to pass any NEW connections through to the underlying driver, bypassing all processing logic. This should only be used in rare situations to debug if the system is causing a problem directly, or the existence of the system is causing a problem.	Boolean	false
Verbose Debug Mode	- (Unlocks below options)	debugMode	In order to diagnose issues with rule processing or other behavior anomalies, this option can be set in order to track the processing of a query through the access layer. This option can cause significantly performance penalties and should be used with caution.	Boolean	false
Connection Handshake Tracing	Access Mode = PostgreSQL Proxy	connectionHandshakeTracingEnabled	Enables detailed logging of the proxy connection handshake process. When this option is turned on, the system records additional diagnostic information for each step involved in establishing a connection to the proxy.	Boolean	false
Lite Debug Mode	-	liteDebug	Works similar to verbose debug mode, doesn't log data all the time, instead keeps it in a buffer for up to a second and dumps all records on an exception.	Boolean	false
Log Methods	Access Mode != JDBC	logMethods	log all JDBC method calls made by an application, excluding those relating to resultSets. Warning!	Boolean	false
Log ResultSet Methods	Log Methods AND Access Mode != JDBC	logResultSetMethods	Include ResultSet operations when logging other methods. Warning!	Boolean	false