zyro

any update on this one? what i am currently seeing with a unique constraint like this (grails-3.3.9/gorm-6.1.11): ``` myOneToOneAssociatedEntity unique: ["mySimpleProperty1", "mySimpleProperty2"] ``` * from the various unique constraints this...

i do not think that this issue is related to the dirty-checking? the question is rather if/how we can handle an `EntityActionVetoException` now that https://hibernate.atlassian.net/browse/HHH-11721 made it into hibernate-5.2.13?

i think this post explains the observed behavior: https://vladmihalcea.com/the-best-way-to-map-a-onetoone-relationship-with-jpa-and-hibernate

just making sure i get that one right - by "former is correct" you mean ```yml dataSources: dataSource: # primary dataSource config ("dataSource") secondary: # secondary dataSource config ("dataSource_secondary") ```...

just a quick note that this is still on the radar, however i am currently using the "legacy" syntax succesfully with gorm-6.1.1 and that is the only working one, at...

just hit this one as well. pull-request targeting `3.0.x` coming up. there it is: #164

thank you for the feedback! really glad to see this plugin is still maintained. sure, i could also send a pr that uses the `persistenceInterceptor` or checks explicitly if the...

similar problem on windows. i think because the redis server executable is run from a varying temp dir (like `c:\users\dummy\appdata\local\temp\1430045057907-0\redis-server-2.8.19.exe`), the windows firewall detects it as "new" application every time...

faced this issue today with a class in a lib jar that used a java 8 method reference (`Foo::bar`)

sample app pushed: https://github.com/zyro23/spring-loaded-138 `gradlew bootRun` should show the exception (grails-app/init/BootStrap.groovy is using `Monetary.getCurrency("USD")`). it is a grails-3.1.0.RC1 app so that should be spring-boot-1.3.1 and spring-loaded-1.2.5