When using GORM outside of Grails in a traditional Spring application as specified here:
an application becomes completely broken when upgrading to 1.3.5 or 1.3.6 from 1.3.4 because the
naming strategy was switched from the default naming strategy to ImprovedNamingStrategy.INSTANCE
without giving the user the ability to configure it back.
This was broken by this commit:
Allow a specifying a naming strategy similar to how you would do it with the spring session factory:
<gorm:sessionFactory id="sessionFactory" base-package="isnotused" data-source-ref="v4DataSource"
<property name="namingStrategy" ref="namingStrategy"/>
<bean id="namingStrategy" class="org.hibernate.cfg.DefaultNamingStrategy"/>
This could be implemented by setting the "naming_strategy" config property inside
such that it can be retrieved by GrailsAnnotationConfiguration.configureNamingStrategy():
Object customStrategy = grailsApplication.getConfig().get("naming_strategy");
I am aware that I can simply add @Column to every one of my properties to get my application to work again, but considering I have over 100 domain classes with at least 10 properties each, this becomes a serious blocker for me.