public interface Statement
Methods of this interface allow to bind argument values to parameters either by name or index.
| Modifier and Type | Method and Description |
|---|---|
ExecutableStatement |
bind(java.util.Map<java.lang.String,java.lang.Object> params)
Binds each parameter by name.
|
ExecutableStatement |
bindByIdx(java.lang.Object... params)
Binds each parameter by index.
|
ExecutableStatement |
noArgs()
Returns a parametrized version of the bindable object without
providing any parameters.
|
java.util.concurrent.CompletionStage<java.lang.Void> |
streamArgs(org.reactivestreams.Publisher<java.util.Map<java.lang.String,java.lang.Object>> paramsPublisher)
Streams statement named arguments to a database.
|
java.util.concurrent.CompletionStage<java.lang.Void> |
streamArgsByIdx(org.reactivestreams.Publisher<java.util.List<java.lang.Object>> paramsPublisher)
Streams statement positional arguments to a database.
|
ExecutableStatement bind(java.util.Map<java.lang.String,java.lang.Object> params) throws NoSuchParamException, MissingParamValException, NoSuitableConverterFoundException
ExecutableStatement bindByIdx(java.lang.Object... params) throws MissingParamValException, NoSuitableConverterFoundException, TooManyParamsException
Parameters are ordered, each value in params sequence will be bound
to the corresponding parameter.
ExecutableStatement noArgs() throws MissingParamValException
MissingParamValExceptionjava.util.concurrent.CompletionStage<java.lang.Void> streamArgs(org.reactivestreams.Publisher<java.util.Map<java.lang.String,java.lang.Object>> paramsPublisher)
This method can be used to repeatedly execute this statement with
published parameters by leveraging Reactive Streams specification's
Publisher with a backpressure. Each published element is a map
containing all parameters required by this statement.
Resulting CompletionStage can fail with:
java.util.concurrent.CompletionStage<java.lang.Void> streamArgsByIdx(org.reactivestreams.Publisher<java.util.List<java.lang.Object>> paramsPublisher)
This method can be used to repeatedly execute this statement with
published parameters by leveraging Reactive Streams specification's
Publisher with a backpressure. Each published element is a map
containing all parameters required by this statement.
Resulting CompletionStage can fail with: