ALTER OPERATOR

Purpose

Use the ALTER OPERATOR statement to add bindings to, drop bindings from, or compile an existing operator.

Prerequisites

The operator must already have been created by a previous CREATE OPERATOR statement. The operator must be in your own schema or you must have the ALTER ANY OPERATOR system privilege. You must have the EXECUTE object privilege on the operators and functions referenced in the ALTER OPERATOR statement.

Syntax

SQLRF52958alter_operator::=

Description of the illustration alter_operator.gif

(add_binding_clause::=, drop_binding_clause::=)

SQLRF52959add_binding_clause::=

Description of the illustration add_binding_clause.gif

(implementation_clause::=, using_function_clause::=)

SQLRF52960implementation_clause::=

Description of the illustration implementation_clause.gif

(context_clause::=)

SQLRF52961context_clause::=

Description of the illustration context_clause.gif

SQLRF52962using_function_clause::=

Description of the illustration using_function_clause.gif

SQLRF52963drop_binding_clause::=

Description of the illustration drop_binding_clause.gif

Semantics

SQLRF52964schema

Specify the schema containing the operator. If you omit this clause, then Oracle Database assumes the operator is in your own schema.

SQLRF52965operator

Specify the name of the operator to be altered.

SQLRF52966add_binding_clause

Use this clause to add an operator binding and specify its parameter data types and return type. The signature must be different from the signature of any existing binding for this operator.

If a binding of an operator is associated with an indextype and you add another binding to the operator, then Oracle Database does not automatically associate the new binding with the indextype. If you want to make such an association, then you must issue an explicit ALTER INDEXTYPE ... ADD OPERATOR statement.

SQLRF52967implementation_clause

This clause has the same semantics in CREATE OPERATOR and ALTER OPERATOR statements. For full information, refer to implementation_clause in the documentation on CREATE OPERATOR.

SQLRF52968context_clause

This clause has the same semantics in CREATE OPERATOR and ALTER OPERATOR statements. For full information, refer to context_clause in the documentation on CREATE OPERATOR.

SQLRF52969using_function_clause

This clause has the same semantics in CREATE OPERATOR and ALTER OPERATOR statements. For full information, refer to using_function_clause in the documentation on CREATE OPERATOR.

SQLRF52970drop_binding_clause

Use this clause to specify the list of parameter data types of the binding you want to drop from the operator. You must specify FORCE if the binding has any dependent objects, such as an indextype or an ancillary operator binding. If you specify FORCE, then Oracle Database marks INVALID all objects that are dependent on the binding. The dependent objects are revalidated the next time they are referenced in a DDL or DML statement or a query.

You cannot use this clause to drop the only binding associated with this operator. Instead you must use the DROP OPERATOR statement. Refer to DROP OPERATOR for more information.

SQLRF52971COMPILE

Specify COMPILE to cause Oracle Database to recompile the operator.

Examples

SQLRF52972Compiling a User-defined Operator: Example The following example compiles the operator eq_op (which was created in "Creating User-Defined Operators: Example"):

ALTER OPERATOR eq_op COMPILE;