pack-priv final Class ParameterImpl<T>

Implements abstract org.jooq.impl.AbstractField.accept.

Implements org.jooq.QueryPartInternal.accept.

Doc from org.jooq.QueryPartInternal.accept.

This QueryPart can accept a Context object in order to render a SQL string or to bind its variables.

Annotations

@Override

Implements org.jooq.Parameter.getParamMode.

Doc from org.jooq.Parameter.getParamMode.

Get the parameter mode for this parameter.

Annotations

@Override

Implements org.jooq.Parameter.isDefaulted.

Doc from org.jooq.Parameter.isDefaulted.

Whether this parameter has a default value

Procedures and functions with defaulted parameters behave slightly different from ones without defaulted parameters. In PL/SQL and other procedural languages, it is possible to pass parameters by name, reordering names and omitting defaulted parameters:

CREATE PROCEDURE MY_PROCEDURE (P_DEFAULTED IN NUMBER := 0
                               P_MANDATORY IN NUMBER);

-- The above procedure can be called as such:
BEGIN
  -- Assign parameters by index
  MY_PROCEDURE(1, 2);

  -- Assign parameters by name
  MY_PROCEDURE(P_DEFAULTED => 1,
               P_MANDATORY => 2);

  -- Omitting defaulted parameters
  MY_PROCEDURE(P_MANDATORY => 2);
END;

If a procedure has defaulted parameters, jOOQ binds them by name, rather than by index.

Currently, this is only supported for Oracle 11g

Annotations

@Override

Implements org.jooq.Parameter.isUnnamed.

Doc from org.jooq.Parameter.isUnnamed.

Whether this parameter has a name or not.

Some databases (e.g. SQLDialect#POSTGRES) allow for using unnamed parameters. In this case, getName() will return a synthetic name created from the parameter index.

Annotations

@Override