Oracle® Call Interface Programmer's Guide 10g Release 1 (10.1) Part Number B10779-01 |
|
|
View PDF |
This appendix provides information about server round trips incurred during various OCI calls. This information can be useful to programmers when determining the most efficient way to accomplish a particular task in an application.
This appendix contains these topics:
This appendix provides information about server round trips incurred during various OCI calls. This information can be useful when determining the most efficient way to accomplish a particular task in an application.
The number of server round trips required by OCI relational functions are listed in Table C-1:
Table C-2 lists the server round trips incurred by the OCILob*()
calls.
Note: To minimize the number of round trips, you can use the data interface for LOBs. You can bind or define character data for a |
See Also:
|
For calls whose number of round trips is "0 or 1", if LOB buffering is on, and the request can be satisfied in the client, no round trips are incurred.
Table C-3 lists the number of server round trips required for the object and cache functions. These values assume the cache is in a warm state, meaning that the type descriptor objects required by the application have been loaded.
The number of server round trips required by OCIDescribeAny()
, OCIAttrGet()
, and OCIParamGet()
are listed in Table C-4:
The number of round trips for the datatype mapping and manipulation functions are listed in Table C-5. The asterisks in the table indicate that all functions with a particular prefix incur the same number of server round trips. For example, OCINumberAdd()
, OCINumberPower()
, and OCINumberFromText()
all incur zero server round trips.
The number of server round trips required by Any Type and Data functions are listed in Table C-6. The functions not listed do not generate any round trips.
The functions listed in Table C-7 are local and do not require a server round trip: