public interface Query extends QueryPart, Attachable
Modifier and Type | Method and Description |
---|---|
Query |
bind(int index,
java.lang.Object value)
Bind a new value to an indexed parameter.
|
Query |
bind(java.lang.String param,
java.lang.Object value)
Bind a new value to a named parameter.
|
void |
cancel()
Cancel the underlying statement.
|
void |
close()
Close the underlying statement.
|
int |
execute()
Execute the query, if it has been created with a proper configuration.
|
java.util.List<java.lang.Object> |
getBindValues()
Retrieve the bind values that will be bound by this Query.
|
Param<?> |
getParam(java.lang.String name)
Get a named parameter from the
Query , provided its name. |
java.util.Map<java.lang.String,Param<?>> |
getParams()
Get a
Map of named parameters. |
java.lang.String |
getSQL()
Retrieve the SQL code rendered by this Query.
|
java.lang.String |
getSQL(boolean inline)
Deprecated.
- [#2414] - 3.1.0 - Use
getSQL(ParamType) instead |
java.lang.String |
getSQL(ParamType paramType)
Retrieve the SQL code rendered by this Query.
|
boolean |
isExecutable()
Whether this query is executable in its current state.
|
Query |
keepStatement(boolean keepStatement)
Keep the query's underlying statement open after execution.
|
Query |
queryTimeout(int timeout)
Specify the query timeout for the underlying JDBC
Statement . |
attach, detach
int execute() throws DataAccessException
Query
:
DataAccessException
- If anything goes wrong in the databaseboolean isExecutable()
java.lang.String getSQL()
Use this method, when you want to use jOOQ for object oriented query creation, but execute the query with some other technology, such as
Note, this is the same as calling getSQL(boolean)
. The boolean
parameter will depend on your DSLContext
's Settings
:
StatementType |
boolean parameter | effect |
---|---|---|
StatementType.PREPARED_STATEMENT |
false (default) |
This will render bind variables to be used with a JDBC
PreparedStatement . You can extract bind values from this
Query using getBindValues() |
StatementType.STATIC_STATEMENT |
true |
This will inline all bind variables in a statement to be used with a
JDBC Statement |
[#1520] Note that the query actually being executed might not contain any
bind variables, in case the number of bind variables exceeds your SQL
dialect's maximum number of supported bind variables. This is not
reflected by this method, which will only use the Settings
to
decide whether to render bind values.
getSQL(boolean)
@Deprecated java.lang.String getSQL(boolean inline)
getSQL(ParamType)
instead
[#1520] Note that the query actually being executed might not contain any
bind variables, in case the number of bind variables exceeds your SQL
dialect's maximum number of supported bind variables. This is not
reflected by this method, which will only use inline
argument to decide whether to render bind values.
See getSQL()
for more details.
inline
- Whether to inline bind variables. This overrides values in
Settings.getStatementType()
java.lang.String getSQL(ParamType paramType)
[#1520] Note that the query actually being executed might not contain any
bind variables, in case the number of bind variables exceeds your SQL
dialect's maximum number of supported bind variables. This is not
reflected by this method, which will only use paramType
argument to decide whether to render bind values.
See getSQL()
for more details.
paramType
- How to render parameters. This overrides values in
Settings.getStatementType()
java.util.List<java.lang.Object> getBindValues()
List
cannot be modified. To modify bind values, use
getParams()
instead.
Unlike getParams()
, which returns also inlined parameters, this
returns only actual bind values that will render an actual bind value as
a question mark "?"
DSLContext.extractBindValues(QueryPart)
java.util.Map<java.lang.String,Param<?>> getParams()
Map
of named parameters. The Map
itself
cannot be modified, but the Param
elements allow for modifying
bind values on an existing Query
.
Bind values created with DSL.val(Object)
will have their bind
index as name.
Param<?> getParam(java.lang.String name)
Query
, provided its name.
Bind values created with DSL.val(Object)
will have their bind
index as name.
Query bind(java.lang.String param, java.lang.Object value) throws java.lang.IllegalArgumentException, DataTypeException
[#1886] If the bind value with name param
is inlined (
Param.isInline()
) or if this query was created with
StatementType.STATIC_STATEMENT
and there is an underlying
PreparedStatement
kept open because of
keepStatement(boolean)
, the underlying
PreparedStatement
will be closed automatically in order for
new bind values to have an effect.
param
- The named parameter name. If this is a number, then this is
the same as calling bind(int, Object)
value
- The new bind value.java.lang.IllegalArgumentException
- if there is no parameter by the given
parameter name or index.DataTypeException
- if value
cannot be converted into
the parameter's data typeQuery bind(int index, java.lang.Object value) throws java.lang.IllegalArgumentException, DataTypeException
[#1886] If the bind value at index
is inlined (
Param.isInline()
) or if this query was created with
StatementType.STATIC_STATEMENT
and there is an underlying
PreparedStatement
kept open because of
keepStatement(boolean)
, the underlying
PreparedStatement
will be closed automatically in order for
new bind values to have an effect.
index
- The parameter index, starting with 1value
- The new bind value.java.lang.IllegalArgumentException
- if there is no parameter by the given
parameter index.DataTypeException
- if value
cannot be converted into
the parameter's data typeQuery queryTimeout(int timeout)
Statement
.Statement.setQueryTimeout(int)
Query keepStatement(boolean keepStatement)
This indicates to jOOQ that the query's underlying Statement
or
PreparedStatement
should be kept open after execution. If it is
kept open, client code is responsible for properly closing it using
close()
keepStatement
- Whether to keep the underlying statement openvoid close() throws DataAccessException
This closes the query's underlying Statement
or
PreparedStatement
if a previous call to
keepStatement(boolean)
indicated that jOOQ should keep
statements open after query execution. If there is no underlying open
statement, this call is simply ignored.
DataAccessException
- If something went wrong closing the statementStatement.close()
void cancel() throws DataAccessException
This cancels the query's underlying Statement
or
PreparedStatement
. If there is no underlying open and running
statement, this call is simply ignored.
DataAccessException
- If something went wrong cancelling the
statementStatement.cancel()
Copyright © 2015. All Rights Reserved.