| java.lang.Object
 org.springframework.orm.jpa.DefaultJpaDialect
All known Subclasses: org.springframework.orm.jpa.vendor.OpenJpaDialect, org.springframework.orm.jpa.vendor.HibernateJpaDialect, org.springframework.orm.jpa.vendor.TopLinkJpaDialect,
| cleanupTransaction | | public void cleanupTransaction(Object transactionData)(Code) | | This implementation does nothing, since the default beginTransaction
implementation does not require any cleanup.
See Also: DefaultJpaDialect.beginTransaction |
| getJdbcConnection | | public ConnectionHandle getJdbcConnection(EntityManager entityManager, boolean readOnly) throws PersistenceException, SQLException(Code) | | This implementation always returns null,
indicating that no JDBC Connection can be provided.
|
| prepareTransaction | | public Object prepareTransaction(EntityManager entityManager, boolean readOnly, String name) throws PersistenceException(Code) | | |
| releaseJdbcConnection | | public void releaseJdbcConnection(ConnectionHandle conHandle, EntityManager em) throws PersistenceException, SQLException(Code) | | This implementation does nothing, assuming that the Connection
will implicitly be closed with the EntityManager.
If the JPA implementation returns a Connection handle that it expects
the application to close after use, the dialect implementation needs to invoke
Connection.close() (or some other method with similar effect) here.
See Also: java.sql.Connection.close |
| supportsEntityManagerFactoryPlusOperations | | public boolean supportsEntityManagerFactoryPlusOperations()(Code) | | |
| supportsEntityManagerPlusOperations | | public boolean supportsEntityManagerPlusOperations()(Code) | | |
|
|