JPA Interface

SchemaManager

Allows programmatic plain, plain, plain, and plain for entities belonging to a certain persistence unit.

Properties are inherited from the EntityManagerFactory, that is, they may be specified via persistence.xml or createEntityManagerFactory().

See Also:
getSchemaManager()
Since:
JPA 3.2

Public Methods

void create(boolean createSchemas)
Create database objects mapped by entities belonging to the persistence unit.

If a DDL operation fails, the behavior is undefined. A provider may throw an exception, or it may ignore the problem and continue.

Parameters:
createSchemas - if {@code true} , attempt to create schemas, otherwise, assume the schemas already exist
Since:
JPA 3.2
void drop(boolean dropSchemas)
Drop database objects mapped by entities belonging to the persistence unit, undoing the effects of the plain.

If a DDL operation fails, the behavior is undefined. A provider may throw an exception, or it may ignore the problem and continue.

Parameters:
dropSchemas - if {@code true} , drop schemas, otherwise, leave them be
Since:
JPA 3.2
void truncate()
Truncate the database tables mapped by entities belonging to the persistence unit, and then re-import initial data from any configured SQL scripts for data loading.

If a SQL operation fails, the behavior is undefined. A provider may throw an exception, or it may ignore the problem and continue.

Since:
JPA 3.2
void validate()
Validate that the database objects mapped by entities belonging to the persistence unit have the expected definitions.

The persistence provider is not required to perform any specific validation, so the semantics of this operation are entirely provider-specific.

Throws:
SchemaValidationException - if a database object is missing or does not have the expected definition
Since:
JPA 3.2