To use this statement, the type of UDR cannot be ambiguous. The UDR that you specify must refer to either a user-defined function or a user-defined procedure. If either of the following conditions exist, the database server returns an error:
If the routine name is not unique within the database, you must specify enough parameter_type information to disambiguate the name. If the database server cannot resolve an ambiguous routine name whose signature differs from that of another routine only in an unnamed ROW type parameter, an error is returned. (This error cannot be anticipated by the database server when the ambiguous routine is defined.)
If you use parameter data types to identify a UDR, they follow the UDR name, as in the following example:
DROP ROUTINE compare(int, int)
If you use the specific name for the UDR, you must also include the keyword SPECIFIC, as in the following example:
DROP SPECIFIC ROUTINE compare_pointEnterprise Edition Home | Express Edition Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]