Forum Discussion
SmartBear_Suppo
Alumni
17 years agoHi,
That happens because currently Groovy method GroovyUtilsPro(...).getGroovySql(...) expects user and password to be specified in connectionString like ...user=something and ...password=something, but oracle specifies them diferently.
This is changed in nightly-build (check it out at http://www.eviware.com/nightly-builds/ ).
Please let us know if it works OK.
Regards,
/Dragica
eviware.com
That happens because currently Groovy method GroovyUtilsPro(...).getGroovySql(...) expects user and password to be specified in connectionString like ...user=something and ...password=something, but oracle specifies them diferently.
This is changed in nightly-build (check it out at http://www.eviware.com/nightly-builds/ ).
Please let us know if it works OK.
Regards,
/Dragica
eviware.com