T
- the result typepublic abstract class MappingSqlQuery<T> extends MappingSqlQueryWithParameters<T>
Simplifies MappingSqlQueryWithParameters API by dropping parameters and context. Most subclasses won't care about parameters. If you don't use contextual information, subclass this instead of MappingSqlQueryWithParameters.
MappingSqlQueryWithParameters
MappingSqlQueryWithParameters.RowMapperImpl
logger
Constructor and Description |
---|
MappingSqlQuery()
Constructor that allows use as a JavaBean.
|
MappingSqlQuery(javax.sql.DataSource ds,
java.lang.String sql)
Convenient constructor with DataSource and SQL string.
|
Modifier and Type | Method and Description |
---|---|
protected abstract T |
mapRow(java.sql.ResultSet rs,
int rowNum)
Subclasses must implement this method to convert each row of the
ResultSet into an object of the result type.
|
protected T |
mapRow(java.sql.ResultSet rs,
int rowNum,
java.lang.Object[] parameters,
java.util.Map<?,?> context)
This method is implemented to invoke the simpler mapRow
template method, ignoring parameters.
|
newRowMapper
execute, execute, execute, execute, execute, execute, execute, execute, execute, execute, execute, execute, executeByNamedParam, executeByNamedParam, findObject, findObject, findObject, findObject, findObject, findObject, findObject, findObject, findObject, findObject, findObjectByNamedParam, findObjectByNamedParam, getRowsExpected, setRowsExpected
compileInternal, getParsedSql, newPreparedStatementCreator, newPreparedStatementCreator, newPreparedStatementSetter, onCompileInternal
afterPropertiesSet, allowsUnusedParameters, checkCompiled, compile, declareParameter, getDeclaredParameters, getGeneratedKeysColumnNames, getJdbcTemplate, getResultSetType, getSql, isCompiled, isReturnGeneratedKeys, isUpdatableResults, resolveSql, setDataSource, setFetchSize, setGeneratedKeysColumnNames, setJdbcTemplate, setMaxRows, setParameters, setQueryTimeout, setResultSetType, setReturnGeneratedKeys, setSql, setTypes, setUpdatableResults, supportsLobParameters, validateNamedParameters, validateParameters
public MappingSqlQuery()
public MappingSqlQuery(javax.sql.DataSource ds, java.lang.String sql)
ds
- the DataSource to use to obtain connectionssql
- the SQL to run@Nullable protected final T mapRow(java.sql.ResultSet rs, int rowNum, @Nullable java.lang.Object[] parameters, @Nullable java.util.Map<?,?> context) throws java.sql.SQLException
mapRow
in class MappingSqlQueryWithParameters<T>
rs
- the ResultSet we're working throughrowNum
- row number (from 0) we're up toparameters
- to the query (passed to the execute() method).
Subclasses are rarely interested in these.
It can be null
if there are no parameters.context
- passed to the execute() method.
It can be null
if no contextual information is need.java.sql.SQLException
- if there's an error extracting data.
Subclasses can simply not catch SQLExceptions, relying on the
framework to clean up.mapRow(ResultSet, int)
@Nullable protected abstract T mapRow(java.sql.ResultSet rs, int rowNum) throws java.sql.SQLException
Subclasses of this class, as opposed to direct subclasses of MappingSqlQueryWithParameters, don't need to concern themselves with the parameters to the execute method of the query object.
rs
- the ResultSet we're working throughrowNum
- row number (from 0) we're up tojava.sql.SQLException
- if there's an error extracting data.
Subclasses can simply not catch SQLExceptions, relying on the
framework to clean up.