Connection String. Idle Timeout, Command Timeout,

dotnetuser

Hi!

Let's compare oracle and npgsql settings

See https://www.npgsql.org/doc/connection-string-parameters.html

1.

<strong>Connection Lifetime vs Connection Idle Lifetime</strong><br/><br/>

Connection Lifetime (oracle)<br/>

Maximum life time (in seconds) of the connection.

Connection Idle Lifetime (npgsql)
The time (in seconds) to wait before closing idle connections in the pool if the count of all connections exceeds Minimum Pool Size. Since 3.1 only.

In the case of npgsql, it is clear what and why.
There is a similar parameter in oracle, but it doesn’t work like that, you need a game with the pool regulator setting in order to add a similar result.

2. Command Timeout

In oracle, there is no such parameter in the connection string, only the class has it.
BUT, if you look at the library code, then it’s clear that this setting creates a timer that dies after a certain step of command execution and there’s little sense in it.

<br/><br/>

Alex Keh-Oracle

You'll see the Connection Lifetime attribute more fully described in the API reference section:

https://docs.oracle.com/en/database/oracle/oracle-data-access-components/19.3/odpnt/ConnectionConnectionString.html#GUID-DF4ED9A3-1AAF-445D-AEEF-016E6CD5A0C0

CommandTimeout is on the OracleCommand object since developers may want to modify the setting over the lifetime of the connection. If the command timeout is on the connection, it must remain the same throughout the connection's lifetime. Moreover, modifying the command timeout creates a new connection pool in the PostgreSQL model. When you modify the CommandTimeout in ODP.NET, no new pool is required. The same pool can be used.