ODPI-C Function Round-Trips¶
The following table identifies if round-trips to the database are required when calling each of the functions that ODPI-C supports. A round-trip is defined as the trip from the Oracle Client libraries (used by ODPI-C) to the database and back.
Function |
Round-Trips? |
Notes |
---|---|---|
No |
||
Yes |
||
Yes |
||
Yes |
||
Maybe |
If the connection was acquired from a pool, a round-trip is only required if the parameter mode is set to the value DPI_MODE_CONN_CLOSE_DROP. For standalone connections, a round-trip is always required. If there is an open transaction, a round-trip is also required to perform the implicit rollback that takes place. |
|
Yes |
||
Maybe |
If a standalone connection is being created, one round-trip is
required. If a connection is being acquired from a pool, no round-trips
are required if an unused connection is available in the pool;
otherwise, a round trip is required for each connection that is added
to the pool (see |
|
Yes |
||
Yes |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
If the type information is already available in the Oracle Client object cache, only one round trip is required; otherwise, two round-trips are required unless the type contains embedded types or is a collection. In that case additional round-trips are required to fetch the additional type information. |
|
No |
||
Maybe |
The first call when requesting the release string always requires a round-trip. If the release string is not requested and Oracle Client 20.3 or higher is being used, no round-trip is required. Similarly for earlier versions, if the release string is not requested and a pooled connection is used that previously had a call to this function made, no round-trip is required; otherwise, a round-trip is required. Subsequent calls with any client version do not require a round-trip. |
|
Maybe |
An internal call to check the server version is made. The notes on the
function |
|
No |
||
No |
||
No |
||
No |
||
No |
||
Yes |
||
No |
||
Yes |
||
Yes |
||
No |
||
Maybe |
If the number of references exceeds 1 or the connection has already
been closed by a call to |
|
Yes |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
No |
||
No |
||
No |
||
Maybe |
A round trip is needed if the JSON data has not yet been fetched from the server. |
|
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
No |
||
No |
||
Maybe |
If the LOB is a temporary LOB, one round-trip is required to free the temporary LOB; otherwise, no round-trips are required. |
|
Yes |
||
Yes |
||
No |
||
Yes |
||
No |
||
Yes |
||
Yes |
||
Yes |
||
No |
||
Yes |
||
Yes |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
Yes |
||
Yes |
||
Yes |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being
released, the internal reference to the object type is the last
reference being released and the object type’s internal reference to
the connection is the last reference to that connection. In that case,
the notes on the function |
|
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being
released, the internal reference to the object type is the last
reference being released and the object type’s internal reference to
the connection is the last reference to that connection. In that case,
the notes on the function |
|
No |
||
No |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
Maybe |
No round-trips are required if an unused connection is available in the
pool; otherwise, a round trip is required for each connection that is
added to the pool (see |
|
No |
||
Maybe |
One round trip is required for each session in the pool that needs to be closed. |
|
Maybe |
One round trip is required for each session that is initially added to
the pool (see |
|
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
If the minimum size of the pool is not being increased, no round-trips are required; otherwise, round-trips are required for each session in the pool that needs to be added to reach the new minimum. |
|
Maybe |
If the number of references exceeds 1 or the pool has already been
closed by a call to |
|
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
No |
||
No |
||
No |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
No |
||
No |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
Yes |
||
Yes |
||
Yes |
||
Yes |
||
Yes |
||
No |
||
No |
||
Yes |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
Maybe |
If the SODA metadata cache has been enabled and no metadata has been specified, a round trip is not required after the first time that a collection with a particular name is opened. |
|
No |
||
No |
||
Yes |
||
Yes |
||
Maybe |
If the SODA metadata cache has been enabled, a round trip is not required after the first time that a collection with a particular name is opened. |
|
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
No |
||
Yes |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Yes |
||
Yes |
||
Maybe |
An internal array of rows corresponding to the value set by a call to
|
|
Maybe |
An internal array of rows corresponding to the value set by a call to
|
|
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
Yes |
||
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
No |
||
No |
||
No |
||
No |
||
No |
||
Maybe |
No round trips are required unless the last reference is being released
and the internal reference to the connection is also the last reference
to that connection. In that case, the notes on the function
|
|
Maybe |
If the variable refers to a LOB, one round-trip is required; otherwise, no round trips are required. |
|
No |
||
No |
||
No |
||
No |
||
No |
||
No |