anchor.diff:  Integrations
   ------------
   
  -Spring-integration
  -~~~~~~~~~~~~~~~~~~
  -
  -Dalesbred has support for integration with Spring Framework and its transaction management.
  -To integrate Dalesbred, create a configuration class inheriting from `DalesbredConfigurationSupport`
  -and specify beans for `DataSource` and `PlatformTransactionManager`. A minimal configuration would
  -therefore be something like the following:
  +Spring
  +~~~~~~
  +
  +Dalesbred has support for integration with http://projects.spring.io/spring-framework/[Spring Framework]
  +and its transaction management. To integrate Dalesbred, create a configuration class inheriting from
  +{javadocBase}fi/evident/dalesbred/support/spring/DalesbredConfigurationSupport.html[DalesbredConfigurationSupport]
  +and specify beans for {jdkJavadocBase}javax/sql/DataSource.html[DataSource] and
  +{springJavadocBase}org/springframework/transaction/PlatformTransactionManager.html[PlatformTransactionManager].
  +A minimal configuration would therefore be something like the following:
   
   [source,java]
   -------------------------------------------------------------------------------------------------------
  
positive.code: });
  -------------------------------------------------------------------------------------------------------
  
  If you make calls to Database without and explicit transaction, by default
  a new transaction is started for each call, but you can disallow this, in
  which case exceptions are thrown for calls without an active transaction:
  
  
negative.code: Map<Integer,String> namesByIds = db.findMap(
          Integer.class, String.class, "select id, name from department");
  
  If for some reason you don't want to map the results into your own class, you can ask for
  a {javadocBase}fi/evident/dalesbred/ResultTable.html[ResultTable], which is basically a detached
  representation of a {jdkJavadocBase}java/sql/ResultSet.html[ResultSet]:
  
  [source,java]
  ResultTable employees = db.findTable("select * from employee");
  
  Alternatively, you can supply your own {javadocBase}fi/evident/dalesbred/results/RowMapper.html[RowMapper] or
  {javadocBase}fi/evident/dalesbred/results/ResultSetProcessor.html[ResultSetProcessor]-implementation in place
  of the class and handle the result sets manually, but usually this should be unnecessary.
  
  Updates
  ~~~~~~~
  