Implementations of this interface perform the actual work of processing each row but don't need to worry about exception handling. SQLExceptions will be caught and handled by the calling JdbcTemplate.
In contrast to a ResultSetExtractor, a RowCallbackHandler object is typically stateful: It keeps the result state within the object, to be available for later inspection.
Consider using a RowMapper instead if you need to map exactly one result object per row, assembling them into a List.
Definition at line 25 of file RowCallbackHandler.java.
Package Functions | |
| void | processRow (ResultSet rs) |
| Implementations must implement this method to process each row of data in the ResultSet. | |
| void liquibase.database.template.RowCallbackHandler.processRow | ( | ResultSet | rs | ) | [package] |
Implementations must implement this method to process each row of data in the ResultSet.
This method should not call next() on the ResultSet; it is only supposed to extract values of the current row.
Exactly what the implementation chooses to do is up to it: A trivial implementation might simply count rows, while another implementation might build an XML document.
| rs | the ResultSet to process (pre-initialized for the current row) |
| java.sql.SQLException | if a SQLException is encountered getting column values (that is, there's no need to catch SQLException) |