Specify the target database to operate on, as a value of the Database enum:
DB2, DERBY, H2, HANA, HSQL, INFORMIX, MYSQL, ORACLE, POSTGRESQL, SQL_SERVER, SYBASE
NOTE: This setting will override your JPA provider's default algorithm.
Custom vendor properties may still fine-tune the database dialect. However,
there may nevertheless be conflicts: For example, specify either this setting
or Hibernate's "hibernate.dialect_resolvers" property, not both.
Return the name of the target database to operate on.
public void setGenerateDdl(boolean generateDdl)
Set whether to generate DDL after the EntityManagerFactory has been initialized,
creating/updating all relevant tables.
Note that the exact semantics of this flag depend on the underlying
persistence provider. For any more advanced needs, specify the appropriate
vendor-specific settings as "jpaProperties".
NOTE: Do not set this flag to 'true' while also setting JPA 2.1's
These two schema generation mechanisms - standard JPA versus provider-native -
are mutually exclusive, e.g. with Hibernate 5.
Return a Map of vendor-specific JPA properties for the given persistence
unit, typically based on settings in this JpaVendorAdapter instance.
Note that there might be further JPA properties defined on the
EntityManagerFactory bean, which might potentially override individual
JPA property values specified here.
This implementation delegates to JpaVendorAdapter.getJpaPropertyMap() for
non-unit-dependent properties. Effectively, this PersistenceUnitInfo-based
variant only needs to be implemented if there is an actual need to react
to unit-specific characteristics such as the transaction type.