This content has been marked as final. Show 2 replies
Interesting. I just reworked our build environment so I can use the Envers schema generator and it dished out the schema as I expected:
create table smx3.contact_mech_versions ( _versions_id int4 not null, contact_mech_id int4, _revision int4 not null, info_string varchar(255), _revision_type int2, contact_mech_type_id int4, primary key (_versions_id), unique (contact_mech_id, _revision) );
Is the hibernate schema generator code using the same VersionsMetadataGenerator that envers uses at run-time?
yes, it's exactly the same. Weird :)
I'll take a look.