java - Why is Hibernate adding schema name to Hsql functions? -


we have legacy app uses hibernate 3.0.3. unit testing hsqldb. 1 of queries generated hibernate looks this:

select  transactio0_.reason_id reason1_0_,  transactio0_.description descript2_93_0_,  transactio0_.reason_name reason3_93_0_  apps.mtl_transaction_reasons transactio0_  transactio0_.reason_id=54  , transactio0_.nvl (transactio0_.disable_date, now() + 1 day) > now() 

note schema name "transactio0_" prepended nvl function. why? how can configure hibernate not that?

the next question deals version of hsqldb using. we're using hsqldb 2.2.8 , move hsqldb 2.3.2. above query works fine hsqldb 2.2.8 fails in hsqldb 2.3.2 "invalid schema name" error. there way can configure hsqldb 2.3.2 can execute query hsqldb 2.2.8 does?

the generated sql looks strange , incorrect sql. transactio0_ table alias , shouldn't prepended function name.

perhaps selected hibernate dialect not hsqldb dialect.

in case, old version of hibernate , needs used version of hsqldb closer time of release.

regarding configuring hsqldb accept malformed name, shouldn't possible original behavior fixed because lax , accepted incorrect sql.


Popular posts from this blog

Apache NiFi ExecuteScript: Groovy script to replace Json values via a mapping file -

python 3.x - PyQt5 - Signal : pyqtSignal no method connect -