zyro
zyro
### Task List - [x] Steps to reproduce provided - [x] Stacktrace (if present) provided - [x] Example that reproduces the problem uploaded to Github - [x] Full description of...
### Task List - [x] Steps to reproduce provided - [x] Stacktrace (if present) provided - [x] Example that reproduces the problem uploaded to Github - [x] Full description of...
this depends on grails/grails-data-mapping#1238 - so if that gets merged, this test will need a corresponding 6.1.12.BUILD-SNAPSHOT
…typed data services works into `Configuration` beans as well as `BeanPostProcessor` beans @puneetbehl looks like the tests pass with gdm-7.0.6 as well (without devtools) because spring already defensively returns null...
configuring two dataSources, * https://github.com/grails/gorm-hibernate5/blob/v6.0.8/docs/src/docs/asciidoc/multipleDataSources/configuration.adoc says ```yml dataSource: # primary dataSource config ("dataSource") dataSources: secondary: # secondary dataSource config ("dataSource_secondary") ``` is the correct format while * http://docs.grails.org/3.2.6/guide/conf.html#multipleDatasources * https://github.com/grails/grails3-functional-tests/blob/3.2.x/datasources/grails-app/conf/application.yml...
if you want to adjust all fields for a certain hasMany association or a collection property, there is no direct way with the existing template lookup. e.g. domain A and...
when constructing the sessionFactory bean name for a secondary dataSource, just append the suffix, not the complete dataSource bean name (i.e. sessionFactory_another instead of sessionFactory_dataSource_another)
### Task List - [x] Steps to reproduce provided - [x] Stacktrace (if present) provided - [ ] Example that reproduces the problem uploaded to Github - [x] Full description...
would be great if this gets released as 1.3.1 or 1.4.0. thank you! i tested locally published to maven local as 1.3.1.BUILD-SNAPSHOT with an app that uses hibernate-5.2 and threw...
for some time now, the quartz plugin already takes care of flushing the session after a job was executed properly using the `HibernatePersistenceContextInterceptor`. and does that in a hibernate-5.2 safe...