Package org.jdbi.v3.core.mapper

Class MapEntryMapper<K,V>

java.lang.Object
org.jdbi.v3.core.mapper.MapEntryMapper<K,V>
Type Parameters:
K - entry key type
V - entry value type
All Implemented Interfaces:
RowMapper<Map.Entry<K,V>>
public class MapEntryMapper<K,V> extends Object implements RowMapper<Map.Entry<K,V>>
Maps rows to Map.Entry<K, V>, provided there are mappers registered for types K and V. This mapper is registered out of the box.

  • Method Details

    • map

      public Map.Entry<K,V> map(ResultSet rs, StatementContext ctx) throws SQLException
      Description copied from interface: RowMapper
      Map the current row of the result set. This method should not cause the result set to advance; allow Jdbi to do that, please.
      Specified by:
      map in interface RowMapper<K>
      Parameters:
      rs - the result set being iterated
      ctx - the statement context
      Returns:
      the value to produce for this row
      Throws:
      SQLException - if anything goes wrong go ahead and let this percolate; Jdbi will handle it

    • specialize

      public RowMapper<Map.Entry<K,V>> specialize(ResultSet rs, StatementContext ctx) throws SQLException
      Description copied from interface: RowMapper
      Returns a specialized row mapper, optimized for the given result set.

      Before mapping the result set from a SQL statement; Jdbi will first call this method to obtain a specialized instance. The returned mapper will then be used to map the result set rows, and discarded.

      Implementing this method is optional; the default implementation returns this. Implementors might choose to override this method to improve performance, e.g. by matching up column names to properties once for the entire result set, rather than repeating the process for every row.

      Specified by:
      specialize in interface RowMapper<K>
      Parameters:
      rs - the result set to specialize over
      ctx - the statement context to specialize over
      Returns:
      a row mapper equivalent to this one, possibly specialized.
      Throws:
      SQLException - if anything goes wrong go ahead and let this percolate; Jdbi will handle it
      See Also: