[hibernate-dev] SchemaManagementTool changes for 5.1 (was Re: 5.1 tentative release date)

Steve Ebersole steve at hibernate.org
Fri Jan 29 13:01:40 EST 2016

On Fri, Jan 29, 2016 at 10:40 AM Gunnar Morling <gunnar at hibernate.org>

> 2016-01-29 17:18 GMT+01:00 Steve Ebersole <steve at hibernate.org>:
> > I also plan on adding an @Incubating annotation for just such things :)
> Yes, please. We have an annotation @Experimental in OGM which we use
> for tagging APIs under development.

See https://hibernate.atlassian.net/browse/HHH-10487.  I also started a
separate discussion about this on the dev list.

BTW, as an extension to changing  SchemaManagementTool another thing I'd
like to add is some hook account for Envers use cases.  Specifically the
idea there is to be able to do a few things:
1) perform a selective create/drop.  selective in terms of just certain
objects.  This may be achievable through the new filter concept, although
we'd at least need a way to identify Envers tables from non-Envers tables.
Think of starting to use Hibernate+Envers on a schema that already exists.
2) perform "actions".  This is maybe beyond "schema tooling"; perhaps it is
more of a SessionFactory boot concept.  But one thing Envers misses today
that would be good to add is the ability to "prime" the audit tables.
Meaning, for audited entities that do not have entries in their audit
table, create one.  This for sure goes beyond simple SQL statements though.

More information about the hibernate-dev mailing list