anchor.diff:  See the <<orm-jpa-dialect, next section>> for details on the `JpaDialect` mechanism.
   
   NOTE: As an immediate alternative, Spring's native `HibernateTransactionManager` is capable
  -of interacting with JPA access code as of Spring Framework 5.1 and Hibernate 5.2/5.3,
  -adapting to several Hibernate specifics and providing JDBC interaction.
  -This makes particular sense in combination with `LocalSessionFactoryBean` setup.
  -See <<orm-jpa-hibernate, Native Hibernate Setup for JPA Interaction>> for details.
  +of interacting with JPA access code, adapting to several Hibernate specifics and providing
  +JDBC interaction. This makes particular sense in combination with `LocalSessionFactoryBean`
  +setup. See <<orm-jpa-hibernate, Native Hibernate Setup for JPA Interaction>> for details.
   
   
   [[orm-jpa-dialect]]
  
positive.code: 	    .bind("tuples", arrayOf(35, 50))
  ----
  
  [[r2dbc-DatbaseClient-filter]]
  ===== Statement Filters
  
  Sometimes it you need to fine-tune options on the actual `Statement`
  
negative.code: [[orm-jpa-hibernate]]
  ==== Native Hibernate Setup and Native Hibernate Transactions for JPA Interaction
  
  A native `LocalSessionFactoryBean` setup in combination with `HibernateTransactionManager`
  allows for interaction with `@PersistenceContext` and other JPA access code. A Hibernate
  `SessionFactory` natively implements JPA's `EntityManagerFactory` interface now
  and a Hibernate `Session` handle natively is a JPA `EntityManager`.
  Spring's JPA support facilities automatically detect native Hibernate sessions.
  