Re: Scripted SQL resource

2017-05-08 Thread Francesco Chicchiriccò
On 08/05/2017 09:37, Mikael Ekblom wrote: Hi, Never mind, I found it. The groovy-script did not like the fact that the columns within the external db resource had different names than the attributes internally defined to be mapped for the user class itself. I solved it by aliasing the

RE: Scripted SQL resource

2017-05-08 Thread Mikael Ekblom
Hi, Never mind, I found it. The groovy-script did not like the fact that the columns within the external db resource had different names than the attributes internally defined to be mapped for the user class itself. I solved it by aliasing the columns from the external db within the query