Skip to Main Content

ODP.NET

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Connection String. Idle Timeout, Command Timeout,

dotnetuserJan 20 2020 — edited Jan 20 2020

Hi!

Let's compare oracle and npgsql settings

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

1.

Connection Lifetime vs Connection Idle Lifetime

Connection Lifetime (oracle)

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.



Comments
Post Details
Added on Jan 20 2020
1 comment
3,116 views