- All Superinterfaces:
QueryPart
,Serializable
,Statement
A step in the construction of the Referencing
SIGNAL SQL STATE
function.
Referencing XYZ*Step
types directly from client code
It is usually not recommended to reference any XYZ*Step
types
directly from client code, or assign them to local variables. When writing
dynamic SQL, creating a statement's components dynamically, and passing them
to the DSL API statically is usually a better choice. See the manual's
section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql.
Drawbacks of referencing the XYZ*Step
types directly:
- They're operating on mutable implementations (as of jOOQ 3.x)
- They're less composable and not easy to get right when dynamic SQL gets complex
- They're less readable
- They might have binary incompatible changes between minor releases
-
Method Summary
Modifier and TypeMethodDescription@NotNull Statement
setMessageText
(String messageText) Add theSET MESSAGE TEXT
clause to theSIGNAL SQL STATE
function.@NotNull Statement
setMessageText
(Field<String> messageText) Add theSET MESSAGE TEXT
clause to theSIGNAL SQL STATE
function.
-
Method Details
-
setMessageText
@Support({DB2,HANA,HSQLDB,MARIADB,MYSQL,POSTGRES,YUGABYTEDB}) @NotNull @CheckReturnValue @NotNull Statement setMessageText(@Param String messageText) Add theSET MESSAGE TEXT
clause to theSIGNAL SQL STATE
function.- Parameters:
messageText
- is wrapped asDSL.val(Object)
.
-
setMessageText
@Support({DB2,HANA,HSQLDB,MARIADB,MYSQL,POSTGRES,YUGABYTEDB}) @NotNull @CheckReturnValue @NotNull Statement setMessageText(Field<String> messageText) Add theSET MESSAGE TEXT
clause to theSIGNAL SQL STATE
function.
-