sqlj.setUDTextName
Argument | Description | Restrictions | Syntax |
---|---|---|---|
class_id | Java™ class that contains the Java™ data type | Qualified name package_id.class_id must not exceed 255 bytes | Language-specific rules for Java™ identifiers |
data_type | User-defined type for which to create a mapping | Name must not exceed 255 bytes | Identifier |
package_id | Name of package that contains the class_id Java™ class | Same length restrictions as class_id | Language-specific rules for Java™ identifiers |
You must have registered the user-defined data type in the CREATE DISTINCT TYPE, CREATE OPAQUE TYPE, or CREATE ROW TYPE statement.
To look up the Java™ class for a user-defined data type, the database server searches in the JAR-file path, which the sqlj.alter_java_path( ) procedure has specified. For more information on the JAR-file path, see sqlj.alter_java_path.
The SQLJ Driver looks in the path that CLASSPATH specifies in the client environment before it asks the database server for the name of the Java™ class.
The setUDTextName( ) routine is an extension to the SQLJ:SQL Routines Using the Java™ Programming Language specification.
If the IFX_EXTEND_ROLE configuration parameter is enabled (which is its default setting), only the DBSA or users who hold the EXTEND role are able to execute the setUDTextName( ) procedure. When IFX_EXTEND_ROLE is disabled, any user can execute setUDTextName( ). (But regardless of the IFX_EXTEND_ROLE setting, you must hold the Resource privilege or the DBA privilege on the database, and also hold the Usage privilege on the Java™ language, before you can create or drop a Java™ UDR.)