Operators can be referenced by indextypes and by SQL queries and DML statements. The operators, in turn, reference functions, packages, types, and other user-defined objects.
To create an operator in your own schema, you must have the
OPERATOR system privilege. To create an operator in another schema, you must have the
OPERATOR system privilege. In either case, you must also have the
EXECUTE object privilege on the functions and operators referenced.
REPLACE to replace the definition of the operator schema object.
Restriction on Replacing an Operator
You can replace the definition only if the operator has no dependent objects, such as indextypes supporting the operator.
Specify the schema containing the operator. If you omit
schema, then the database creates the operator in your own schema.
Specify the name of the operator to be created. The name must satisfy the requirements listed in "Database Object Naming Rules".
binding_clause to specify one or more parameter data types (
parameter_type) for binding the operator to a function. The signature of each binding—the sequence of the data types of the arguments to the corresponding function—must be unique according to the rules of overloading.
parameter_type can itself be an object type. If it is, then you can optionally qualify it with its schema.
Restriction on Binding Operators
You cannot specify a
Oracle Database PL/SQL Language Reference for more information about overloading
Specify the return data type for the binding.
return_type can itself be an object type. If so, then you can optionally qualify it with its schema.
Restriction on Binding Return Data Type
You cannot specify a
ANCILLARY TO Clause
TO clause to indicate that the operator binding is ancillary to the specified primary operator binding (
primary_operator). If you specify this clause, then do not specify a previous binding with just one number parameter.
context_clause to describe the functional implementation of a binding that is not ancillary to a primary operator binding.
WITH INDEX CONTEXT, SCAN CONTEXT
Use this clause to indicate that the functional evaluation of the operator uses the index and a scan context that is specified by the implementation type.
COMPUTE ANCILLARY DATA
DATA to indicate that the operator binding computes ancillary data.
WITH COLUMN CONTEXT
CONTEXT to indicate that Oracle Database should pass the column information to the functional implementation for the operator.
If you specify this clause, then the signature of the function implemented must include one extra
Oracle Database Data Cartridge Developer's Guide for instructions on using the
using_function_clause lets you specify the function that provides the implementation for the binding. The
function_name can be a standalone function, packaged function, type method, or a synonym for any of these.
If the function is subsequently dropped, then the database marks all dependent objects
INVALID, including the operator. However, if you then subsequently issue an
BINDING statement to drop the binding, then subsequent queries and DML will revalidate the dependent objects.
Creating User-Defined Operators: Example
This example creates a very simple functional implementation of equality and then creates an operator that uses the function. For a more complete set of examples, see Oracle Database Data Cartridge Developer's Guide.
CREATE FUNCTION eq_f(a VARCHAR2, b VARCHAR2) RETURN NUMBER AS BEGIN IF a = b THEN RETURN 1; ELSE RETURN 0; END IF; END; / CREATE OPERATOR eq_op BINDING (VARCHAR2, VARCHAR2) RETURN NUMBER USING eq_f;