(1) |--+-| Adding or Modifying a Routine Modifier |------+----------| '-| Dropping a Routine Modifier |-----------------' Dropping a Routine Modifier: (2) (3) |--+-+---------------+-----+--VARIANT-+-+-----------------------| | | '-NOT-' | | | '-NEGATOR------------------------' | | (4) | +--------+-CLASS----------+----------+ | +-ITERATOR-------+ | | '-PARALLELIZABLE-' | | (2) | '--------+-HANDLESNULLS-+------------' +-INTERNAL-----+ +-PERCALL_COST-+ +-+-SELFUNC--+-+ | '-SELCONST-' | '-STACK--------'
Element | Description | Restrictions | Syntax |
---|---|---|---|
parameter | Name that you declare here for a returned parameter of the UDR | Must be unique among returned parameters of UDRs. If any returned value of the UDR has a name, then all must have names. | Identifier |
If you drop an existing modifier in an ALTER FUNCTION, ALTER PROCEDURE, or ALTER ROUTINE statement, the database server sets the value of the modifier to the default value, if a default exists.
Some modifiers are available only with user-defined functions. For information on whether a specific routine modifier applies only to user-defined functions (that is, if it does not apply to user-defined procedures), see the description of the modifier in the sections that follow. In these sections, as elsewhere in this manual, external refers to UDRs written in the C or Java languages. Features valid for only one language are so designated in the previous diagrams.
Except for VARIANT and NOT VARIANT modifiers, none of the options in this segment are valid for SPL routines.
Enterprise Edition Home | Express Edition Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]