I have built a DelegatingReverseEngineeringStrategy that has me 95% where I need to be
(I need to periodically reverse engineer a 500+ entitiy schema that is externally configuration managed and changes on about a 6 month cycle.)
My problem is that the Oracle 11 validator interface is a little particular about numeric datatypes. I have been able to work around these anomolies 100% of the time by adding
Code:
columnDefinition("NUMBER(11,5)")
to the
Code:
@Column
attribute, for example. I am at a loss as to where to put this in my Custom Strategy. I think the method might be columnToMetaAttribute(), but unlike ColumnToHibernateTypeName, columnToMetaAttributes does not have the precision and scale passed to it.
Is there an "approved" way to add the columnDefinition attribute? Since columnToMetaAttributes is called immediately after columnToHibernateTypeName, I can temporarily store the most recent type, percision and scale for later use in columnToMetaAttributes; though that is a little shady.
If there is not an approved way, I'll have to write an application to post-process; It would be wonderful to be able to get things done in one pass, though. Any ideas? (Honestly I did look at documentation, but I was either not finding it or the Custom Strategy docs are less-than-verbose).
Cordially,
Mark Henning