...
Database Type | Properties | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CSV | All properties described on the page http://csvjdbc.sourceforge.net/doc.html in the section section "Driver Properties" can be used. | ||||||||||||
MySQL | mysql.connectionpool.maxlimit | ||||||||||||
Oracle | oracle.pool.connectionwaittimeout oracle.pool.inactivitytimeout oracle.pool.maxlimit oracle.pool.minlimit oracle.pool.propertycheckinterval oracle.pool.refreshonsqlerror oracle.net.encryption_client oracle.net.encryption_types_client oracle.net.crypto_checksum_client oracle.net.crypto_checksum_types_client | ||||||||||||
PostgreSQL |
| PostgreSQL >= 11 |
| |
From PostgreSQL 11 onwards, there is support for stored PROCEDURE, |
prior versions of PostgreSQL supports only |
the stored FUNCTION. Hence, a new connection property called "escapeSyntaxCallMode" has been introduced by PostgreSQL for users to configure. This property specifies how the driver transforms JDBC escape call syntax into underlying SQL, for invoking procedures or functions.
|
|
In case you are using Callable Statements with PostgreSQL, you can configure the “escapeSyntaxCallMode” connection property in the Database Profile. However, If this property is not configured in the Database Profile, it will be using the default escapeSyntaxCallMode=select. If you're utilizing Callable Statements with PostgreSQL, you have the option to set |
the "escapeSyntaxCallMode" property either within the Connection String parameters or within the Properties tab of the Database Profile. Should you choose to configure this property in both locations, priority will be given to the setting within the Connection String. |
sapdb.connectionpool.maxlimit
...