- All Implemented Interfaces:
- Serializable,- Binding<XML,- Node> 
- Author:
- Lukas Eder
- See Also:
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptionstatic DocumentBuilderbuilder()Get a namespace-aware document builderA converter that can convert between the database type and the custom type.static DocumentfromString(String name) Create a new DOM element in an independent documentfinal voidGet aResultSet'sOUTvalue.final voidget(BindingGetSQLInputContext<Node> ctx) Get aSQLInput'sOUTvalue.final voidGet aCallableStatement'sOUTvalue.final voidRegister aCallableStatement'sOUTparameter.final voidSet aSQLOutput'sINparameter.final voidSet aPreparedStatement'sINparameter.final voidsql(BindingSQLContext<Node> ctx) Generate SQL code for the bind variable.
- 
Constructor Details- 
XMLasDOMBindingpublic XMLasDOMBinding()
 
- 
- 
Method Details- 
converterDescription copied from interface:BindingA converter that can convert between the database type and the custom type.While the Converterproperty of a binding is not optional (Converter.fromType()andConverter.toType()are needed by jOOQ's internals), the conversion implementation (i.e.Converter.from(Object)andConverter.to(Object)) isn't strictly required if implementations don't rely on it. If these conversion implementations are non-functional, it is advised to hint at this fact inConverter.fromSupported()andConverter.toSupported().
- 
fromStringCreate a new DOM element in an independent document
- 
builderGet a namespace-aware document builder
- 
sqlDescription copied from interface:BindingGenerate SQL code for the bind variable.Implementations should generate SQL code onto BindingSQLContext.render(), given the context's bind variable located atBindingSQLContext.value(). Examples of such SQL code are:- "?": Default implementations can simply generate a question mark.
 
 
- "123": Implementations may choose to inline bind variables to influence execution plan generation.
 
 - Context.paramType()contains information whether inlined bind variables are expected in the current context.
 
 
- "CAST(? AS DATE)": Cast a database to a more specific type. This can be useful in databases like Oracle, which map both- DATEand- TIMESTAMPSQL types to- Timestamp.
 
 - Context.castMode()may contain some hints about whether casting is suggested in the current context.
 
 
- "?::json": Vendor-specific bind variables can be supported, e.g.- SQLDialect.POSTGRES's JSON data type.
 Implementations must provide consistent behaviour between Binding.sql(BindingSQLContext)andBinding.set(BindingSetStatementContext), i.e. when bind variables are inlined, then they must not be bound to thePreparedStatementinBinding.set(BindingSetStatementContext)- Specified by:
- sqlin interface- Binding<XML,- T> 
- Parameters:
- ctx- The context object containing all argument objects.
- Throws:
- SQLException- Implementations are allowed to pass on all- SQLExceptions to the caller to be wrapped in- DataAccessExceptions.
 
- 
registerDescription copied from interface:BindingRegister aCallableStatement'sOUTparameter.- Specified by:
- registerin interface- Binding<XML,- T> 
- Parameters:
- ctx- The context object containing all argument objects.
- Throws:
- SQLException- Implementations are allowed to pass on all- SQLExceptions to the caller to be wrapped in- DataAccessExceptions.
 
- 
setDescription copied from interface:BindingSet aPreparedStatement'sINparameter.- Specified by:
- setin interface- Binding<XML,- T> 
- Parameters:
- ctx- The context object containing all argument objects.
- Throws:
- SQLException- Implementations are allowed to pass on all- SQLExceptions to the caller to be wrapped in- DataAccessExceptions.
 
- 
getDescription copied from interface:BindingGet aResultSet'sOUTvalue.Implementations are expected to produce a value by calling BindingGetResultSetContext.value(Object), passing the resulting value to the method.- Specified by:
- getin interface- Binding<XML,- T> 
- Parameters:
- ctx- The context object containing all argument objects.
- Throws:
- SQLException- Implementations are allowed to pass on all- SQLExceptions to the caller to be wrapped in- DataAccessExceptions.
 
- 
getDescription copied from interface:BindingGet aCallableStatement'sOUTvalue.Implementations are expected to produce a value by calling BindingGetStatementContext.value(Object), passing the resulting value to the method.- Specified by:
- getin interface- Binding<XML,- T> 
- Parameters:
- ctx- The context object containing all argument objects.
- Throws:
- SQLException- Implementations are allowed to pass on all- SQLExceptions to the caller to be wrapped in- DataAccessExceptions.
 
- 
setDescription copied from interface:BindingSet aSQLOutput'sINparameter.- Specified by:
- setin interface- Binding<XML,- T> 
- Parameters:
- ctx- The context object containing all argument objects.
- Throws:
- SQLException- Implementations are allowed to pass on all- SQLExceptions to the caller to be wrapped in- DataAccessExceptions.
 
- 
getDescription copied from interface:BindingGet aSQLInput'sOUTvalue.Implementations are expected to produce a value by calling BindingGetSQLInputContext.value(Object), passing the resulting value to the method.- Specified by:
- getin interface- Binding<XML,- T> 
- Parameters:
- ctx- The context object containing all argument objects.
- Throws:
- SQLException- Implementations are allowed to pass on all- SQLExceptions to the caller to be wrapped in- DataAccessExceptions.
 
 
-