Release 8.1.5
A67846-01
 Library |
 Product |
 Contents |
 Index |
| Oracle Call Interface Programmer's Guide Release 8.1.5 A67846-01 |
|
This chapter introduces the OCI's facility for working with objects in an Oracle database server. It also discusses the OCI's object navigational function calls. The following sections are included in this chapter:
Note: The functionality described in this chapter is only available if you have installed the Oracle8i Enterprise Edition.
This chapter is divided into several sections that cover the basic concepts involved in writing OCI applications to manipulate Oracle objects and the OCI navigational function calls.
The following chapters contain additional information about using the OCI to work with objects:
Complete descriptions of the OCI object-relational functions are contained in Chapter 16, "OCI Navigational and Type Functions", and Chapter 17, "OCI Datatype Mapping and Manipulation Functions". Additionally, some object functionality is included in those functions described in Chapter 15, "OCI Relational Functions".
The Oracle Call Interface (OCI) provides functions for managing database access and processing SQL statements. These functions are described in detail in Part I of this guide. The SQL capabilities of the OCI relational interface allow an application to access objects from an Oracle database server through SQL statements.
The OCI allows applications to access any of the datatypes found in the Oracle database server, including scalar values, collections, and instances of any object type. This includes all of the following:
To take full advantage of Oracle server object capabilities, most applications need to do more than just access objects. After an object has been retrieved, the application must navigate through references from that object to other objects. The OCI provides the capability to do this. Through the OCI's object navigational calls, an application can perform any of the following functions on Oracle objects:
The OCI navigational calls are discussed in more detail later in this chapter.
The OCI also provides the ability to access type information stored in an Oracle database. The OCIDescribeAny() function enables an application to access most information relating to types stored in the database, including information about methods, attributes, and type meta-data. OCIDescribeAny() is discussed in Chapter 6, "Describing Schema Metadata".
Applications interacting with Oracle objects need a way to represent those objects in a host language format. Oracle8i provides a utility called the Object Type Translator (OTT), which can convert type definitions in the database to C struct declarations. The declarations are stored in a header file that can be included in an OCI application.
When type definitions are represented in C, the types of attributes are mapped to special C variable types that are new to Oracle8i. The OCI includes a set of datatype mapping and manipulation functions that enable an application to manipulate these datatypes, and thus manipulate the attributes of objects. These functions are discussed in more detail in Chapter 11, "Object-Relational Datatypes".
The terminology for objects can occasionally become confusing. In the remainder of this chapter, the terms object and instance both refer to an object that is either stored in the database or is present in the object cache.
Many of the programming principles that govern a relational OCI application (as discussed in Chapter 2 through 6) are the same for an object-relational application. An object-relational application uses the standard OCI calls to establish database connections and process SQL statements. The difference is that the SQL statements issued retrieve object references (or objects by value), which can then be manipulated with the OCI's object functions.
The basic structure of an OCI application that uses objects is essentially the same as that for a relational OCI application, as described in the section "OCI Program Structure". That paradigm is reproduced here, with extra information covering basic object functionality.
Note: You must initialize the environment in object mode.
Your application will most likely also need to include C struct representations of database objects in a header file. These structs can be created by the programmer, or, more easily, they can be generated by the Object Type Translator (OTT), as described in Chapter 14, "Using the Object Type Translator".
Note: It is also possible to fetch an entire object, rather than just a reference (REF). If you SELECT a referenceable object, rather than pinning it, you get that object by value. Alternately, you can select a non-referenceable object, as described in "Fetching Embedded Objects"
In an object-relational application, this step entails retrieving the REF, and then pinning the object to which it refers. Once the object is pinned, your application will do some or all of the following:
All of these steps are discussed in more detail in the remainder of this chapter.
See Also: For information about using the OCI to connect to a server, process SQL statements, and allocate handles, see Chapter 2, "OCI Programming Basics" and the description of the OCI relational functions in Chapter 15, "OCI Relational Functions".
For information about the OTT, refer to the section "Representing Objects in C Applications", and Chapter 14, "Using the Object Type Translator".
Instances of an Oracle type are categorized into persistent objects and transient objects based on their lifetime. Instances of persistent objects can be further divided into standalone objects and embedded objects depending on whether or not they are referenceable by way of an object identifier.
Note: The terms object and instance are used interchangeably in this manual.
See Also: For more information about objects, refer to the Oracle8i Concepts manual.
A persistent object is an object which is stored in an Oracle database. It may be fetched into the object cache and modified by an OCI application. The lifetime of a persistent object can exceed that of the application which is accessing it. Once it is created, it remains in the database until it is explicitly deleted. There are two types of persistent objects:
It is also possible to SELECT a referenceable object, in which case you fetch the object by value instead of fetching its REF.
Embedded objects may also be referred to as non-referenceable objects or value instances. You may sometimes see them referred to as values, which is not to be confused with scalar data values. The context should make the meaning clear.
The following SQL examples demonstrate the difference between these two types of persistent objects.
CREATE TYPE person_t AS OBJECT (name varchar2(30), age number(3)); CREATE TABLE person_tab OF person_t;
Objects which are stored in the object table person_tab are standalone instances. They have object identifiers and are referenceable. They can be pinned in an OCI application.
CREATE TABLE department (deptno number, deptname varchar2(30), manager person_t);
Objects which are stored in the manager column of the department table are embedded objects. They do not have object identifiers, and they are not referenceable. This means they cannot be pinned in an OCI application, and they also never need to be unpinned. They are always retrieved into the object cache by value.
A transient object is an instance of an object type. It may have an object identifier, and it has a lifetime which is determined by the application when the instance is created. The application can also delete a transient object at any time.
Transient objects are often created by the application using the OCIObjectNew() function to store temporary values for computation. Transient objects cannot be converted to persistent objects. Their role is fixed at the time they are instantiated.
See Also: See the section "Creating Objects" for more information about using OCIObjectNew().
In the context of this manual, a value refers to either:
The context should make it clear which meaning is intended.
Note: It is possible to SELECT a referenceable object into the object cache, rather than pinning it, in which case you fetch the object by value instead of fetching its REF.
This section discusses the steps involved in developing a basic OCI object application. Each step discussed in the section "Basic Object Program Structure" is described here in more detail.
The following figure shows a simple program logic flow for how an application might work with objects. For simplicity, some required steps are omitted. Each step in this diagram is discussed in the following sections.
Before an OCI application can work with object types, those types must exist in the database. Typically, you create types with SQL DDL statements, such as CREATE TYPE.
When the Oracle server processes the type definition DDL commands, it stores the type definitions in the data dictionary as type descriptor objects (TDOs).
When your application retrieves instances of object types from the database, it needs to have a client-side representation of the objects. In a C program, the representation of an object type is a struct. In an OCI object application, you may also include a null indicator structure corresponding to each object type structure.
Note: Application programmers who wish to utilize object representations other than the default structs generated by the object cache should refer to "The Object Cache and Memory Management".
Oracle8i provides a utility called the Object Type Translator (OTT), which generates C struct representations of database object types for you. For example, if you have a type in your database declared as
CREATE TYPE emp_t AS OBJECT ( name VARCHAR2(30), empno NUMBER, deptno NUMBER, hiredate DATE, salary NUMBER);
the OTT produces the following C struct and corresponding null indicator struct:
struct emp_t { OCIString * name; OCINumber empno; OCINumber deptno; OCIDate hiredate; OCINumber salary; }; typedef struct emp_t emp_t struct emp_t_ind { OCIInd _atomic; OCIInd name; OCIInd empno; OCIInd deptno; OCIInd hiredate; OCIInd salary; }; typedef struct emp_t_ind emp_t_ind;
The variable types used in the struct declarations are special types employed by the OCI object calls. A subset of OCI functions manipulate data of these types. These functions are mentioned later in this chapter, and are discussed in more detail in Chapter 11, "Object-Relational Datatypes".
These struct declarations are automatically written to a .h file whose name is determined by the OTT input parameters. You can include this header file in the code files for an application to provide access to objects.
See Also: For more information about the OTT, see Chapter 14, "Using the Object Type Translator".
For more information on the use of the NULL indicator struct, see the section "Nullness".
If your OCI application will be accessing and manipulating objects, it is essential that you specify a value of OCI_OBJECT for the mode parameter of the OCIInitialize() call, which is the first OCI call in any OCI application. Specifying this value for mode indicates to the OCI libraries that your application will be working with objects. This notification has the following important effects:
If the mode parameter of OCIInitialize() is not set to OCI_OBJECT, any attempt to use an object-related function will result in an error.
The client-side object cache is allocated in the program's process space. This cache is the memory for objects that have been retrieved from the server and are available to your application.
Note: If you initialize the OCI environment in object mode, your application allocates memory for the object cache, whether or not the application actually uses object calls.
See Also: The object cache is mentioned throughout this chapter. For a detailed explanation of the object cache, see Chapter 13, "Object Cache and Object Navigation".
Once the OCI environment has been properly initialized, the application can connect to a server. This is accomplished through the standard OCI connect calls described in "OCI Programming Steps". When using these calls, no additional considerations need to be made because this application will be accessing objects.
There is only one object cache allocated per OCI environment. All objects retrieved or created via different connections within the environment use the same physical object cache.
In order to work with objects, your application must first retrieve one or more objects from the server. You accomplish this by issuing a SQL statement that returns REFs to one or more objects.
Note: It is also possible for a SQL statement to fetch embedded objects, rather than REFs, from a database. See the section "Fetching Embedded Objects" for more information.
In the following example, the application declares a text block that stores a SQL statement designed to retrieve a REF to a single employee object from a object table of employees (emp_tab) in the database, given a particular employee number which is passed as an input variable (:emp_num) at run time:
text *selemp = (text *) "SELECT REF(e) FROM emp_tab e WHERE empno = :emp_num";
Your application should prepare and process this statement in the same way that it would handle any relational SQL statement, as described in Chapter 2:
OCIRef *emp1_ref = (OCIRef *) 0; /* reference to an employee object */
When defining the output variable, set the dty datatype parameter for the define call to SQLT_REF, the datatype constant for REF.
emp1_ref, using OCIStmtFetch().
At this point, you could use the object reference to access and manipulate an object or objects from the database.
See Also: For general information about preparing and executing SQL statements, see the section "OCI Programming Steps". For specific information about binding and defining REF variables, refer to the sections "Advanced Bind Operations" and "Advanced Define Operations".
For a code example showing REF retrieval and pinning, see the demonstration programs included with your Oracle installation. For additional information, refer to Appendix B, "OCI Demonstration Programs".
Upon completion of the fetch step, your application has a REF, or pointer, to an object. The actual object is not currently available to work with. Before you can manipulate an object, it must be pinned. Pinning an object loads the object instance into the object cache, and enables you to access and modify the instance's attributes and follow references from that object to other objects, if necessary. Your application also controls when modified objects are written back to the server.
Note: This section deals with a simple pin operation involving a single object at a time. For information about retrieving multiple objects through complex object retrieval, see the section "Complex Object Retrieval".
An application pins an object by calling the function OCIObjectPin(). The parameters for this function allow you to specify the pin option, pin duration, and lock option for the object.
The following sample code illustrates a pin operation for the employee reference we retrieved in the previous section:
if (OCIObjectPin(env, err, &emp1_ref, (OCIComplexObject *) 0, OCI_PIN_ANY, OCI_DURATION_TRANS, OCI_LOCK_X, &emp1) != OCI_SUCCESS) process_error(err);
In this example, process_error() represents an error-handling function. If the call to OCIObjectPin() returns anything but OCI_SUCCESS, the error-handling function is called. The parameters of the OCIObjectPin() function are as follows:
env is the OCI environment handle.
err is the OCI error handle.
emp1_ref is the reference that was retrieved through SQL.
(OCIComplexObject *) 0 indicates that this pin operation is not utilizing complex object retrieval.
OCI_PIN_ANY is the pin option. See "Pinning an Object Copy" for more information.
OCI_DURATION_TRANS is the pin duration. See "Object Duration" for more information.
OCI_LOCK_X is the lock option. See "Locking Objects For Update" for more information.
emp1 is an out parameter, which returns a pointer to the pinned object.
Now that the object has been pinned, the OCI application can modify that object. In this simple example, the object contains no references to other objects. For an example of navigation from one instance to another, see the section "Simple Object Navigation".
Given an array of references, an OCI application can pin an array of objects by calling OCIObjectArrayPin(). The references may point to objects of different types.
Once an object has been pinned, an OCI application can modify its attributes. The OCI provides a set of function for working with datatypes of object type structs, known as the OCI datatype mapping and manipulation functions.
Note: Changes made to objects pinned in the object cache affect only those object copies (instances), and not the original object in the database. In order for changes made by the application to reach the database, those changes must be flushed/committed to the server. See "Marking Objects and Flushing Changes" for more information.
For example, assume that the employee object in the previous section was pinned so that the employee's salary could be increased. Assume also that at this company, yearly salary increases are prorated for employees who have been at the company for less than 180 days.
For this example we will need to access the employee's hire date and check whether it is more or less than 180 days prior to the current date. Based on that calculation, the employee's salary is increased by either $5000 (for more than 180 days) or $3000 (for less than 180 days). The sample code on the following page demonstrates this process.
Note that the datatype mapping and manipulation functions work with a specific set of datatypes; you must convert other types, like int, to the appropriate OCI types before using them in calculations.
/* assume that sysdate has been fetched into sys_date, a string. */ /* emp1 and emp1_ref are the same as in previous sections. */ /* err is the OCI error handle. */ /* NOTE: error handling code is not included in this example. */ sb4 num_days; /* the number of days between today and hiredate */ OCIDate curr_date; /* holds the current date for calculations */ int raise; /* holds the employee's raise amount before calculations */ OCINumber raise_num; /* holds employee's raise for calculations */ OCINumber new_sal; /* holds the employee's new salary */ /* convert date string to an OCIDate */ OCIDateFromText(err, (text *) sys_date, (ub4) strlen(sys_date), (text *) NULL, (ub1) 0, (text *) NULL, (ub4) 0, &curr_date); /* get number of days between hire date and today */ OCIDateDaysBetween(err, &curr_date, &emp1->hiredate, &num_days); /* calculate raise based on number of days since hiredate */ if num_days > 180 raise = 5000 else raise = 3000; /* convert raise value to an OCINumber */ OCINumberFromInt(err, (dvoid *)&raise, (uword)sizeof(raise), OCI_NUMBER_SIGNED, &raise_num); /* add raise amount to salary */ OCINumberAdd(err, &raise_num, &emp1->salary, &new_sal); OCINumberAssign(err, &new_sal, &emp1->salary);
This example points out how values must be converted to OCI datatypes (e.g., OCIDate, OCINumber) before being passed as parameters to the OCI datatype mapping and manipulation functions.
See Also: For more information about the OCI datatypes and the datatype mapping and manipulation functions, refer to Chapter 11, "Object-Relational Datatypes".
In the example in the previous section, an attribute of an object instance was changed. At this point, however, that change exists only in the client-side object cache. The application must take specific steps to insure that the change is written in the database.
The first step is to indicate that the object has been modified. This is done with the OCIObjectMarkUpdate() function. This function marks the object as dirty (modified).
Objects that have had their dirty flag set must be flushed to the server for the changes to be recorded in the database. You can do this in three ways:
The flush operations work only on persistent objects in the cache. Transient objects are never flushed to the server.
Flushing an object to the server can activate triggers in the database. In fact, on some occasions an application may want to explicitly flush objects just to fire triggers on the server side.
See Also: For more information about OCITransCommit() see the section "Transactions".
For information about transient and persistent objects, see the section "Creating Objects".
For information about seeing and checking object meta-attributes, such as dirty, see the section "Object Meta-Attributes".
If your application needs to fetch an embedded object instance--an object stored in a column of a regular table, rather than an object table--you cannot use the REF retrieval mechanism described in the section "Retrieving an Object Reference from the Server". Embedded instances do not have object identifiers, so it is not possible to get a REF to them. This means that they cannot serve as the basis for object navigation. There are still many situations, however, in which an application will want to fetch embedded instances.
For example, assume that an address type has been created.
CREATE TYPE address AS OBJECT ( street1 varchar2(50), street2 varchar2(50), city varchar2(30), state char(2), zip number(5))
You could then use that type as the datatype of a column in another table:
CREATE TABLE clients ( name varchar2(40), addr address)
Your OCI application could then issue the following SQL statement:
SELECT addr FROM clients WHERE name='BEAR BYTE DATA MANAGEMENT'
This statement would return an embedded address object from the clients table. The application could then use the values in the attributes of this object for other processing.
Your application should prepare and process this statement in the same way that it would handle any relational SQL statement, as described in Chapter 2:
address instance. You use a C struct representation of the object type that was generated by the OTT, as described in the section "Representing Objects in C Applications":
addr1 *address; /* variable of the address struct type */
When defining the output variable, set the dty datatype parameter for the define call to SQLT_NTY, the datatype constant for named data types.
addr1, using OCIStmtFetch().
Following this, you can access the attributes of the instance, as described in the section "Manipulating Object Attributes", or pass the instance as an input parameter for another SQL statement.
Note: Changes made to an embedded instance can be made persistent only by executing a SQL UPDATE statement.
See Also: For more information about preparing and executing SQL statements, see the section "OCI Programming Steps".
An object's meta-attributes serve as flags which can provide information to an application, or to the object cache, about the status of an object. For example, one of the meta-attributes of an object indicates whether or not it has been flushed to the server. These can help an application control the behavior of instances.
Persistent and transient object instances have different sets of meta-attributes. The meta-attributes for persistent objects are further broken down into persistent meta-attributes and transient meta-attributes. Transient meta-attributes exist only when an instance is in memory. Persistent meta-attributes also apply to objects stored in the server.
The following table shows the meta-attributes for standalone persistent objects.
Note: Embedded persistent objects only have the nullness and allocation duration attributes, which are transient.
The OCI provides the OCIObjectGetProperty() function, which allows an application to check the status of a variety of attributes of an object. The syntax of the function is:
sword OCIObjectGetProperty ( OCIEnv *envh, OCIError *errh, CONST dvoid *obj, OCIObjectPropId propertyId, dvoid *property, ub4 *size );
The propertyId and property parameters are used to retrieve information about any of a variety of properties or attributes
The different property ids and the corresponding type of property argument are given below. For more information, see OCIObjectGetProperty().
This identifies whether the given object is a persistent object or a transient object or a value instance. The property argument must be a pointer to a variable of type OCIObjectLifetime. Possible values include:
This returns the schema name of the table in which the object exists. An error is returned if the given object points to a transient instance or a value. If the input buffer is not big enough to hold the schema name an error is returned, the error message will communicate the required size. Upon success, the size of the returned schema name in bytes is returned via size. The property argument must be an array of type text and size should be set to size of array in bytes by the caller.
This returns the table name in which the object exists. An error is returned if the given object points to a transient instance or a value. If the input buffer is not big enough to hold the table name an error is returned, the error message will communicate the required size. Upon success, the size of the returned table name in bytes is returned via size. The property argument must be an array of type text and size should be set to size of array in bytes by the caller.
This returns the pin duration of the object. An error is returned if the given object points to a value instance. The property argument must be a pointer to a variable of type OCIDuration. Valid values include:
For more information about durations, see "Object Duration".
This returns the allocation duration of the object. The property argument must be a pointer to a variable of type OCIDuration. Valid values include:
For more information about durations, see "Object Duration".
This returns the lock status of the object. The possible lock status is enumerated by OCILockOpt. An error is returned if the given object points to a transient or value instance. The property argument must be a pointer to a variable of type OCILockOpt. Note, the lock status of an object can also be retrieved by calling OCIObjectIsLocked().
This returns the dirty status and indicates whether the object is a new object, updated object or deleted object. An error is returned if the given object points to a transient or value instance. The property argument must be of type OCIObjectMarkStatus. Valid values include:
The following macros are available to test the object mark status:
This identifies whether the specified object is a view object or not. If the property value returned is TRUE, it indicates the object is a view otherwise it is not. An error is returned if the given object points to a transient or value instance. The property argument must be of type boolean.
The OCI also provides routines which allow an application to set or check some of these attributes directly or indirectly, as shown in the following table:
| Meta-Attribute | Set With | Check With |
|---|---|---|
|
nullness |
<none> |
OCIObjectGetInd() |
|
existence |
<none> |
OCIObjectExists() |
|
locked |
OCIObjectLock() |
OCIObjectIsLocked() |
|
dirty |
OCIObjectMark() |
OCIObjectIsDirty() |
Transient objects have no persistent attributes, and the following transient attributes:
In the examples earlier in this chapter, only a single instance at a time was fetched or pinned. In these cases, each pin operation involved a separate server round trip to retrieve the object.
Object-oriented applications often model their problems as a set of interrelated objects that form graphs of objects. The applications process objects by starting at some initial set of objects, and then using the references in these initial objects to traverse the remaining objects. In a client-server setting, each of these traversals could result in costly network roundtrips to fetch objects.
Application performance when dealing with objects may be increased through the use of complex object retrieval (COR). This is a prefetching mechanism in which an application specifies a criteria for retrieving a set of linked objects in a single operation.
Note: As described below, this does not mean that these prefetched objects are all pinned. They are fetched into the object cache, so that subsequent pin calls are local operations.
A complex object is a set of logically related objects consisting of a root object, and a set of objects each of which is prefetched based on a given depth level. The root object is explicitly fetched or pinned. The depth level is the shortest number of references that need to be traversed from the root object to a given prefetched object in a complex object.
An application specifies a complex object by describing its content and boundary. The fetching of complex objects is constrained by an environment's prefetch limit, the amount of memory in the object cache that is available for prefetching objects.
Note: The use of COR does not add functionality; it only improves performance so its use is optional.
As an example for this discussion, consider the following type declaration:
CREATE TYPE customer(...); CREATE TYPE line_item(...); CREATE TYPE line_item_varray as VARRAY(100) of REF line_item; CREATE TYPE purchase_order AS OBJECT ( po_number NUMBER, cust REF customer, related_orders REF purchase_order, line_items line_item_varray)
The purchase_order type contains a scalar value for po_number, a VARRAY of line items, and two references. The first is to a customer type, and the second is to a purchase_order type, indicating that this type may be implemented as a linked list.
When fetching a complex object, an application must specify the following:
In the case of the purchase order object above, the application must specify the following:
cust, related_orders, or line_items
An application fetching a purchase order will very likely need access to the customer information for that order. Using simple navigation, this would require two server accesses to retrieve the two objects. Through complex object retrieval, the customer can be prefetched when the application pins the purchase order. In this case, the complex object would consist of the purchase order object and the customer object it references.
In the previous example, the application would specify the purchase_order REF, and would indicate that the cust REF attribute should be followed to a depth level of 1:
If the application wanted to prefetch the purchase_order object and all objects in the object graph it contains, the application would specify that both the cust and related_orders should be followed to the maximum depth level possible.
where UB4MAXVAL specifies that all objects of the specified type reachable through references from the root object should be prefetched.
If an application wanted to fetch a PO and all the associated line items, it would specify:
The application can also choose to fetch all objects reachable from the root object by way of REFs (transitive closure) to a certain depth. To do so, set the level parameter to the depth desired. For the above two examples, the application could also specify (PO object REF, UB4MAXVAL) and (PO object REF, 1) respectively to prefetch required objects. Doing so results in many extraneous fetches but is quite simple to specify, and requires only one server round trip.
After specifying and fetching a complex object, subsequent fetches of objects contained in the complex object do not incur the cost of a network round trip, because these objects have already been prefetched and are in the object cache. Keep in mind that excessive prefetching of objects can lead to a flooding of the object cache. This flooding, in turn, may force out other objects that the application had already pinned leading to a performance degradation instead of performance improvement.
Note: If there is insufficient memory in the cache to hold all prefetched objects, some objects may not be prefetched. The application will then incur a network round-trip when those objects are accessed later.
The SELECT privilege is needed for all prefetched objects. Objects in the complex object for which the application does not have SELECT privilege will not be prefetched.
Complex Object Retrieval (COR) allows an application to prefetch a complex object while fetching the root object. The complex object specifications are passed to the same OCIObjectPin() function used for simple objects.
An application specifies the parameters for complex object retrieval using a complex object retrieval handle. This handle is of type OCIComplexObject and is allocated in the same way as other OCI handles.
The complex object retrieval handle contains a list of complex object retrieval descriptors. The descriptors are of type OCIComplexObjectComp, and are allocated in the same way as other OCI descriptors.
Each COR descriptor contains a type REF and a depth level. The type REF specifies a type of reference to be followed while constructing the complex object. The depth level indicates how far a particular type of reference should be followed. Specify an integer value, or the constant UB4MAXVAL for the maximum possible depth level.
The application can also specify the depth level in the COR handle without creating COR descriptors for type and depth parameters. In this case, all REFs are followed to the depth specified in the COR handle. The COR handle can also be used to specify whether a collection attribute should be fetched separately on demand (out-of-line) as opposed to the default case of fetching it along with the containing object (inline).
The application uses OCIAttrSet() to set the attributes of a COR handle. The attributes are:
OCI_ATTR_COMPLEXOBJECT_LEVEL - the depth level
OCI_ATTR_COMPLEXOBJECT_COLL_OUTOFLINE - fetch collection attribute in an object type out-of-line
The application allocates the COR descriptor using OCIDescriptorAlloc() and then can set the following attributes:
OCI_ATTR_COMPLEXOBJECTCOMP_TYPE - the type REF
OCI_ATTR_COMPLEXOBJECTCOMP_LEVEL - the depth level for references of the above type
Once these attributes are set, the application calls OCIParamSet() to put the descriptor into a complex object retrieval handle. The handle has an OCI_ATTR_PARAM_COUNT attribute which specifies the number of descriptors on the handle. This attribute can be read with OCIAttrGet().
Once the handle has been populated, it can be passed to the OCIObjectPin() call to pin the root object and prefetch the remainder of the complex object.
The complex object retrieval handles and descriptors must be freed explicitly when they are no longer needed.
See Also: For more information about handles and descriptors, see "Handles" and "Descriptors and Locators".
The application specifies a complex object while fetching the root object. The prefetched objects are obtained by doing a breadth-first traversal of the graph(s) of objects rooted at a given root object(s). The traversal stops when all required objects have been prefetched, or when the total size of all the prefetched objects exceeds the prefetch limit.
The interface for fetching complex objects is the OCI pin interface. The application can pass an initialized COR handle to OCIObjectPin() (or an array of handles to OCIObjectArrayPin()) to fetch the root object and the prefetched objects specified in the COR handle.
sword OCIObjectPin ( OCIEnv *env, OCIError *err, OCIRef *object_ref, OCIComplexObject *corhdl, OCIPinOpt pin_option, OCIDuration pin_duration, OCILockOpt lock_option, dvoid **object ); sword OCIObjectArrayPin ( OCIEnv *env, OCIError *err, OCIRef **ref_array, ub4 array_size, OCIComplexObject **cor_array, ub4 cor_array_size, OCIPinOpt pin_option, OCIDuration pin_duration, OCILockOpt lock, dvoid **obj_array, ub4 *pos );
Note the following points when using COR:
Note: In order to specify lock options for prefetched objects, the application can visit all the objects in a complex object, create an array of REFs, and lock the entire complex object in another round trip using the array interface (OCIObjectArrayPin()).
The following example illustrates how an application program can be modified to use complex object retrieval.
Consider an application that displays a purchase order and the line items associated with it. The code in boldface accomplishes this. The rest of the code uses complex object retrieval for prefetching and thus enhances the application's performance.
OCIEnv *envhp; OCIError *errhp; OCIRef *liref; OCIRef *poref; OCIIter *itr; boolean eoc; purchase_order *po = (purchase_order *)0; line_item *li = (line_item *)0; OCISvcCtx *svchp; OCIComplexObject *corhp; OCIComplexObjectComp *cordp; OCIType *litdo; ub4 level = 0; /* get COR Handle */ OCIHandleAlloc((dvoid *) envhp, (dvoid **) &corhp, (ub4) OCI_HTYPE_COMPLEXOBJECT, 0, (dvoid **)0); /* get COR descriptor for type line_item */ OCIDescriptorAlloc((dvoid *) envhp, (dvoid **) &cordp, (ub4) OCI_DTYPE_COMPLEXOBJECTCOMP, 0, (dvoid **) 0); /* get type of line_item to set in COR descriptor */ OCITypeByName(envhp, errhp, svchp, (const text *) 0, (ub4) 0, const text *) "LINE_ITEM", (ub4) strlen((const char *) "LINE_ITEM"), OCI_DURATION_SESSION, &litdo); /* set line_item type in COR descriptor */ OCIAttrSet( (dvoid *) cordp, (ub4) OCI_DTYPE_COMPLEXOBJECTCOMP, dvoid *) litdo, (ub4) sizeof(dvoid *), (ub4) OCI_ATTR_COMPLEXOBJECTCOMP_TYPE, (OCIError *) errhp); level = 1; /* set depth level for line_item_varray in COR descriptor */ OCIAttrSet( (dvoid *) cordp, (ub4) OCI_DTYPE_COMPLEXOBJECTCOMP, (dvoid *) &level, (ub4) sizeof(ub4), (ub4) OCI_ATTR_COMPLEXOBJECTCOMP_TYPE_LEVEL, (OCIError *) errhp); /* put COR descriptor in COR handle */ OCIParamSet(corhp, OCI_HTYPE_COMPLEXOBJECT, &errhp, cordp, OCI_DTYPE_COMPLEXOBJECTCOMP, 1); /* pin the purchase order */ OCIObjectPin(envhp, errhp, poref, corhp, OCI_PIN_LATEST, OCI_REFRESH_LOADED, OCI_DURATION_SESSION, OCI_LOCK_NONE, (ub2) 1, (dvoid **)&po) /* free COR descriptor and COR handle */ OCIDescriptorFree((dvoid *) cordp, (ub4) OCI_DTYPE_COMPLEXOBJECTCOMP); OCIHandleFree((dvoid *) corhp, (ub4) OCI_HTYPE_COMPLEXOBJECT); /* iterate and print line items for this purchase order */ OCIIterCreate(envhp, errhp, po.line_items, &itr); /* get first line item */ OCIIterNext(envhp, errhp, itr, &liref, (dvoid **)0, &eoc); while (!eoc) /* not end of collection */ { /* pin line item */ OCIObjectPin(envhp, errhp, liref, (dvoid *)0, OCI_PIN_RECENT, OCI_REFRESH_LOADED, OCI_DURATION_SESSION, OCI_LOCK_NONE, (ub2) 1, (dvoid **)&li); display_line_item(li); /* get next line item */ OCIIterNext(envhp, errhp, itr, &liref, (dvoid **)0, &eoc); }
If an application needs to manipulate a graph of objects (inter-related via object references) then it is more effective to use the OCI interface rather than the SQL interface for accessing objects. Retrieving a graph of objects using the SQL interface may require executing multiple SELECT statements which would mean multiple network roundtrips. Using the complex object retrieval capability provided by the OCI, the application can retrieve the graph of objects in one OCIObjectPin() call.
Consider the update case where the application retrieves a graph of objects and modifies it based upon user interaction and then wishes to make the modifications persistent in the database. Using the SQL interface, the application would have to execute multiple UPDATE statements to update the graph of objects. If the modifications involved creation of new objects and deletion of existing objects then corresponding INSERT and DELETE statements would also need to be executed. In addition, the application would have to do more bookkeeping, such as keeping track of table names, because this information is required for executing the INSERT/UPDATE/DELETE statements.
Using the OCI's OCICacheFlush() function, the application can flush all modifications (insertion, deletion and update of objects) in a single operation. The OCI does all the bookkeeping, thereby requiring less coding on the part of the application. So for manipulating graph of objects the OCI is not only efficient but also provides an easy to use interface.
Consider a different case in which the application needs to fetch an object given its REF. In the OCI this is achieved by pinning the object via the OCIObjectPin() call. In the SQL interface this can be achieved by dereferencing the REF in a SELECT statement (e.g. SELECT DEREF(ref) from tbl;). Consider situations where the same REF (i.e. reference to the same object) is being dereferenced multiple times in a transaction. By calling OCIObjectPin() with the OCI_PIN_RECENT option, the object will be fetched from the server only once for the transaction and repeated pins on the same REF result in returning a pointer to the already-pinned object in the cache. In the case of the SQL interface, each execution of the SELECT DEREF... statement would result in fetching the object from the server and hence would result in multiple roundtrips to the server and multiple copies of the same object.
Finally, consider the case in which the application needs to fetch a non-referenceable object. For example,
CREATE TABLE department ( deptno number, deptname varchar2(30), manager employee_t );
employee_t instances stored in the manager column are non-referenceable. Only the SQL interface can be used to fetch manager column instances. But if employee_t has any REF attributes, OCI calls can then be used to navigate the REF.
Each object in the object cache has a pin count associated with it. The pin count essentially indicates the number of code modules that are concurrently accessing the object. The pin count is set to 1 when an object is pinned into the cache for the first time. Objects prefetched with complex object retrieval enter the object cache with a pin count of zero.
It is possible to pin an already-pinned object. Doing so increases the pin count by one. When a process finishes using an object, it should unpin it, using OCIObjectUnpin(). This call decrements the pin count by one.
When the pin count of an object reaches zero, that object is eligible to be aged out of the cache if necessary, freeing up the memory space occupied by the object.
The pin count of an object can be set to zero explicitly by calling OCIObjectPinCountReset().
An application can unpin all objects in the cache related to a specific connection, by calling OCICacheUnpin().
See Also: See the section "Freeing an Object Copy" for more information about the conditions under which objects with zero pin count are removed from the cache.
For information about explicitly flushing an object or the entire cache, see the section "Marking Objects and Flushing Changes".
See the section "Freeing an Object Copy" for more information about objects being aged out of the cache.
If a column in a row of a database table has no value, then that column is said to be NULL, or to contain a NULL. Two different types of nulls can apply to objects:
Atomic nullness is not the same thing as nonexistence. An atomically null instance still exists, its value is just not known. It may be thought of as an existing object with no data.
When working with objects in the OCI, an application can define a null indicator structure for each object type used by the application. In most cases, doing so simply requires including the null indicator structure generated by the OTT along with the struct declaration. When the OTT output header file is included, the null indicator struct becomes available to your application.
For each type, the null indicator structure includes an atomic null indicator (whose type is OCIInd), and a null indicator for each attribute of the instance. If the type has an object attribute, the null indicator structure includes that attribute's null indicator structure. The following example shows the C representations of types with their corresponding null indicator structures.
struct address { OCINumber no; OCIString *street; OCIString *state; OCIString *zip; }; typedef struct address address; struct address_ind { OCIInd _atomic; OCIInd no; OCIInd street; OCIInd state; OCIInd zip; }; typedef struct address_ind address_ind; struct person { OCIString *fname; OCIString *lname; OCINumber age; OCIDate birthday; OCIArray *dependentsAge; OCITable *prevAddr; OCIRaw *comment1; OCILobLocator *comment2; address addr; OCIRef *spouse; }; typedef struct person person; struct person_ind { OCIInd _atomic; OCIInd fname; OCIInd lname; OCIInd age; OCIInd birthday; OCIInd dependentsAge; OCIInd prevAddr; OCIInd comment1; OCIInd comment2; address_ind addr; OCIInd spouse; }; typedef struct person_ind person_ind;
Note: The dependentsAge field of person_ind indicates whether the entire varray (dependentsAge field of person) is atomically null or not. Null information of individual elements of dependentsAge can be retrieved through the elemind parameter of a call to OCICollGetElem(). Similarly, the prevAddr field of person_ind indicates whether the entire nested table (prevAddr field of person) is atomically null or not. Null information of individual elements of prevAddr can be retrieved through the elemind parameter of a call to OCICollGetElem().
For an object type instance, the first field of the null-indicator structure is the atomic null indicator, and the remaining fields are the attribute null indicators whose layout resembles the layout of the object type instance's attributes.
Checking the value of the atomic null indicator allows an application to test whether an instance is atomically NULL. Checking any of the others allows an application to test the NULL status of that attribute, as in the following code sample:
person_ind *my_person_ind if ( my_person_ind -> _atomic = OCI_IND_NULL) { /* instance is atomically null */ } if ( my_person_ind -> fname = OCI_IND_NULL) { /* fname attribute is NULL */ }
In the above example, the value of the atomic null indicator, or one of the attribute null indicators, is compared to the predefined value OCI_IND_NULL to test its nullness. The following predefined values are available for such a comparison:
Use the OCIObjectGetInd() function to allocate storage for and retrieve the null indicator structure of an object.
See Also: For more information about OTT-generated null indicator structs, refer to Chapter 14, "Using the Object Type Translator".
An OCI application can create any object using OCIObjectPin(). To create a persistent object, the application must specify the object table where the new object will reside. This value can be retrieved by calling OCIObjectPinTable(), and it is passed in the table parameter. To create a transient object, the application needs to pass only the type descriptor object (retrieved by calling OCITypeByName()) for the type of object being created.
OCIObjectNew() can also be used to create instances of scalars (e.g., REF, LOB, string, raw, number, and date) and collections (e.g., varray and nested table) by passing the appropriate value for the typecode parameter.
By default, all attributes of a newly created objects have NULL values. After initializing attribute data, the user must change the corresponding NULL status of each attribute to non-NULL.
It is possible to have attributes set to non-NULL values when an object is created. This is accomplished by setting the OCI_OBJECT_NEWNOTNULL attribute of the environment handle to TRUE using OCIAttrSet(). This mode can later be turned off by setting the attribute to FALSE.
If OCI_OBJECT_NEWNOTNULL is set to TRUE, then OCIObjectNew() creates a non-null object. The attributes of the object have the default values described in the following table, and the corresponding null indicators are set to not-NULL.
Use OCIObjectFree() to free memory allocated through OCIObjectNew(). Freeing an object deallocates all the memory allocated for the object, including the associated null indicator structure. This procedure deletes an object before its lifetime expires. An application can also use OCIObjectMarkDelete() to delete a persistent object.
An application can copy one instance to another instance of the same type using OCIObjectCopy().
See Also: See the descriptions of these functions in Chapter 16, "OCI Navigational and Type Functions" for more information.
The object extensions to the OCI provide the application with the flexibility to access the contents of objects using their pointers or their references. The OCI provides the function OCIObjectGetObjectRef() to return a reference to an object given the object's pointer.
For applications that also want to access the type information of objects, the OCI provides the function OCIObjectGetProperty() to return a reference to an object's type descriptor object (TDO), given a pointer to the object.
Applications can use the OCIObjectNew() call to create objects which are based on object views, or on tables with user-defined OIDs. If OCIObjectNew() receives a handle to an object view or a table with a user-defined OID, then the reference it returns is a pseudo-reference. This pseudo-reference cannot be saved into any other object, but it can be used to fill in the object's attributes so that a primary-key-based reference can be obtained with OCIObjectGetObjectRef().
This process involves the following steps:
The following sample code shows how this process might be implemented to create a new object for the emp_view object view in the scott schema:
void object_view_new () { dvoid *table; OCIRef *pkref; dvoid *object; .... /* Set up the service context, error handle etc.. */ ... /* Pin the object view */ OCIObjectPinTable(envp,errorp,svctx, "scott", strlen("scott"), "emp_view", strlen("emp_view"),(dvoid *) 0, OCI_DURATION_SESSION, (dvoid **) &table); /* Create a new object instance */ OCIObjectNew(envp, errorp, svctx, OCI_TYPECODE_OBJECT,(OCIType *)0, table, OCI_DURATION_SESSION,FALSE,&object); /* Populate the attributes of "object" */ OCIObjectSetAttr(...); ... /* Allocate an object reference */ OCIObjectNew(envp, errorp, svctx, OCI_TYPECODE_REF, (OCIType *)0, (dvoid *)0, OCI_DURATION_SESSION,TRUE,&pkref); /* Get the reference using OCIObjectGetObjectRef */ OCIObjectGetObjectRef(envp,errorp,object,pkref); ... /* Flush new object(s) to server */ ... } /* end function */
Error handling in OCI applications is the same, whether or not the application uses objects. For more information about function return codes and error messages, see the section "Error Handling".
