Format
CHANGE GENERIC type-name element-name
[ DESCRIPTION IS /*text*/ ]
[ NODESCRIPTION ] [ AUDIT IS /*text*/ ]
[ ]
[ {n } ]
[ property-name IS {quoted-string } ] ... .
[ { } ]
[ NOproperty-name ]
[ DEFINE relationship-name relationship-mbr
[ {n } ]
[ property-name IS {quoted-string } ] ... .
[ { } ]
[ NOproperty-name ]
END relationship-name DEFINE . ] ...
[ DELETE relationship-name relationship-mbr . ] ...
END [ element-name ] type-name .
1 – Parameters
1.1 – type-name
Specifies the type of the generic element you are modifying.
This type cannot be MCS_BINARY, a subtype of MCS_BINARY, MCS_
COLLECTION, MCS_CONTEXT, or MCS_PARTITION. See the Oracle
CDD/Repository Information Model Volume I for more information.
1.2 – element-name
Specifies the generic element you are modifying.
1.3 – text
Modifies information. Within the DESCRIPTION clause, this is
information documenting the generic element; within the AUDIT
clause, it is a history list entry. Valid delimiters are /* */ or
double quotation marks (" ").
You can use Japanese to document comments in the DESCRIPTION or
AUDIT clause for a field. To do this, use the SET CHARACTER_SET
command, and set the character_set of the session to DEC_KANJI.
1.4 – property-name
Specifies the property you are adding, changing, or removing. You
specify removal with the NO keyword.
1.5 – n
Modifies the value (numerical) set for a property.
1.6 – quoted-string
Modifies the value (a string enclosed in quotation marks) set for
a property.
1.7 – relationship-name
Specifies the relationship type that you are defining or deleting
in the generic element. The type must be a subtype of RELATION.
1.8 – relationship-mbr
Specifies the generic element that you are defining or deleting
as a member of the relationship type. The element must exist in
the repository; otherwise, an error occurs.
2 – Description
The CHANGE GENERIC command modifies a generic element by
performing a change in place. CDO changes the values you specify,
and other values remain the same.
If a generic element is a controlled versioned element, CDO
freezes previous versions and allows you to modify only the
highest visible version. If a generic element is an uncontrolled
versioned element, CDO modifies the highest version unless you
specify another version number.
If a generic element is controlled, you must reserve the element
before you can issue the CHANGE GENERIC command. The SHOW GENERIC
or SHOW RESERVATIONS command indicates whether this condition
exists.
You can modify generic elements that are based on types supplied
through Oracle CDD/Repository or on user-supplied (extended)
types. If you do most of your work with extended types, Oracle
recommends that you should work through the Oracle CDD/Repository
callable interface. The CDO GENERIC commands are useful to modify
and display on a spot basis, but extensibility is not supported
through CDO.
If you add, change, or delete a property from the generic
element, the property you specify must be a defined or inherited
property for the element's type. Likewise, any relationship
member you specify must be compatible with the relationship
name's type. See the Oracle CDD/Repository Information Model
Volume I for more information on valid properties and types.
If the generic element you are modifying is based on an extended
type and errors occur when you attempt to add or delete a
relationship, you may not have specified the processing name
property as a required property for your type. The property takes
a quoted string value.
CAUTION
Specify the MCS_processingName property, not the
CDD$PROCESSING_NAME property, when you work with extended
types. Otherwise, you experience performance degradation in
the Oracle CDD/Repository callable interface.
The type on which the generic element definition is based
determines whether an attribute is required or optional in
instances of the type. If the type definition specifies that the
CDD$DESCRIPTION attribute can be used in instances of the type,
you can add documentation text to the generic entity definition
or remove existing documentation text. You can display text
entered with the DESCRIPTION clause by using the SHOW GENERIC
command with the /BRIEF or /FULL qualifiers.
If the type definition specifies that the CDD$HISTORY_LIST
relationship can be used in instances of the type, you can
add explanatory history list entries to the generic entity
definition. You can display history list entries for generic
entity definitions by using the SHOW GENERIC command with the
/AUDIT or /ALL qualifiers.
3 – Examples
1.CDO> CHANGE GENERIC CDD$EXECUTABLE_IMAGE MY_PROGRAM
cont> MCS_PROCESSINGNAME "OUR_PROGRAM".
cont> END MY_PROGRAM CDD$EXECUTABLE_IMAGE.
In this example, the CHANGE GENERIC command modifies the
MCS$PROCESSING_NAME (MCS_processingName property) of the
generic element MY_PROGRAM. MY_PROGRAM is based on the
type CDD$EXECUTABLE_IMAGE, which is supplied by Oracle
CDD/Repository.
2.CDO> CHANGE GENERIC BOOK CDO_REFERENCE_MANUAL
cont> LIBRARY_NUMBER IS "AA-KL45A-TF".
cont> END BOOK CDO_REFERENCE_MANUAL.
In this example, the CHANGE GENERIC command modifies the
LIBRARY_NUMBER of the CDO_REFERENCE_MANUAL generic element.
CDO_REFERENCE_MANUAL is based on the user-supplied type BOOK.