In the meantime (to get the builds working again) I went ahead and
implemented the explicit checking. If you want to change something
there, just look for usages of the new
org.hibernate.envers.configuration.internal.metadata.FormulaNotSupportedException.
There are only 2 places it is used,
Hi Lukasz,
The problems seem limited to usages of:
1)
org.hibernate.envers.configuration.internal.metadata.MetadataTools#getColumnNameIterator
2)
org.hibernate.envers.configuration.internal.metadata.MetadataTools#addColumns
from:
1)
org.hibernate.envers.configuration.internal.metadata.AuditMe
Hello Steve,
In general Envers does not support formula columns. Probably we should save
formula value to audit table. This can be tricky and I have to think it
over. Copying formula column to audit entity would not produce expected
result in all cases (e.g. time functions used in formula expressi
One option just came to mind. Looking at the code, I have to assume
envers really just does not support formulas. Otherwise, all these
compile errors would eventually have resulted in runtime (CCE)
exceptions.
If that is really the case, I could add detection of that and throw a
more meaning
