Oracle8i SQL Reference Release 3 (8.1.7) Part Number A85397-01 |
|
SQL Statements:
CREATE SYNONYM to DROP ROLLBACK SEGMENT, 8 of 31
Use the CREATE
TYPE
BODY
to define or implement the member methods defined in the object type specification. You create object types with the CREATE
TYPE
and the CREATE
TYPE
BODY
statements. The CREATE
TYPE
statement specifies the name of the object type, its attributes, methods, and other properties. The CREATE
TYPE
BODY
statement contains the code for the methods in the type.
For each method specified in an object type specification for which you did not specify the call_spec
, you must specify a corresponding method body in the object type body.
Every member declaration in the CREATE
TYPE
specification for object types must have a corresponding construct in the CREATE
TYPE
or CREATE
TYPE
BODY
statement.
To create or replace a type body in your own schema, you must have the CREATE
TYPE
or the CREATE
ANY
TYPE
system privilege. To create an object type in another user's schema, you must have the CREATE
ANY
TYPE
system privileges. To replace an object type in another user's schema, you must have the DROP
ANY
TYPE
system privileges.
procedure_declaration | function_declaration::=
Java_declaration
::=
C_declaration
::=
OR
REPLACE
Specify OR
REPLACE
to re-create the type body if it already exists. Use this clause to change the definition of an existing type body without first dropping it.
Users previously granted privileges on the re-created object type body can use and reference the object type body without being granted privileges again.
You can use this clause to add new member subprogram definitions to specifications added with the ALTER
TYPE
... REPLACE
statement.
schema
Specify the schema to contain the type body. If you omit schema
, Oracle creates the type body in your current schema.
type_name
Specify the name of an object type.
IS
| AS
|
Specify the type of method function or procedure subprogram associated with the object type specification. |
|
|
You must define a corresponding method name, optional parameter list, and (for functions) a return type in the object type specification for each procedure or function declaration. |
|
|
|
Declare a procedure subprogram. |
|
|
Declare a function subprogram. |
|
|
MAP
| ORDER
|
Specify |
|
|
If the argument to the map method is null, the map method returns null and the method is not invoked. |
|
|
An object type body can contain only one map method, which must be a function. The map function can have no arguments other than the implicit |
|
|
Specify |
|
|
If either argument to the order method is null, the order method returns null and the method is not invoked.
When instances of the same object type definition are compared in an |
|
|
An object specification can contain only one |
|
You can declare either a |
||
If you do not declare either method, you can compare object instances only for equality or inequality. Instances of the same type definition are equal only if each pair of their corresponding attributes is equal. |
||
|
Declare a procedure or function subprogram. The
|
|
|
|
Declare the procedure or function.
|
|
|
Specify the call specification ("call spec") that maps a Java or C method name, parameter types, and return type to their SQL counterparts.
In
|
|
|
|
The following object type body implements member subprograms for rational
. (PL/SQL is shown in italics.)
CREATE TYPE BODY rational IS MAP MEMBER FUNCTION rat_to_real RETURN REAL IS BEGIN RETURN numerator/denominator; END; MEMBER PROCEDURE normalize IS gcd NUMBER := integer_operations.greatest_common_divisor (numerator, denominator); BEGIN numerator := numerator/gcd; denominator := denominator/gcd; END; MEMBER FUNCTION plus(x rational) RETURN rational IS r rational := rational_operations.make_rational (numerator*x.denominator + x.numerator*denominator, denominator*x.denominator); BEGIN RETURN r; END; END;
|
![]() Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
|