Help Center> GaussDB> Centralized_3.x> Application Development Guide> Development Specifications
Updated on 2024-05-07 GMT+08:00
View PDF

Development Specifications

If the connection pool mechanism is used during application development, comply with the following specifications:
  • If GUC parameters are set in the connection, run SET SESSION AUTHORIZATION DEFAULT;RESET ALL; to clear the connection status before you return the connection to the connection pool.
  • If a temporary table is used, delete the temporary table before you return the connection to the connection pool.

If you do not do so, the connection state in the connection pool will remain, which affects subsequent operations using the connection pool.

Table 1 describes the compatibility of application development drivers.
Table 1 Compatibility Description

Driver

Compatibility Description

JDBC and Go

The new drivers are forward compatible with the database. To use the new features added to the driver and database, you must upgrade the database.

ODBC, libpq, Psycopg, and ecpg

The driver version must match the database version.
  • Setting behavior_compat_options to 'proc_outparam_override' is applicable only in A-compatible mode.
  • In principle, you need to set the compatibility parameter after the database creation, instead of switching the parameters when using the database.
  • The JDBC driver must be upgraded to that maps to GaussDB Kernel 503.1 or later if the following features are used:
    • The s2 compatibility parameter is enabled and the validity check of sessiontimezone is set.

If the driver is used in a multi-thread environment:

The JDBC driver is non-thread-safe and does not guarantee that the connection methods are synchronized. The caller synchronizes the calls to the driver.