Hi there,

we have a project setup with Hibernate 4 and Hibernate Spatial using a Postgresql database with the PostGIS extension. Currently we are migrating to Hibernate 5 and tackled some problems so far.
But now we ran into an issue with log messages provided by JDBCDSLOG. When previously using Hibernate 4 with Hibernate Spatial, JDBCDSLOG was logging geometries as WKT, this was possible as it received the SQL parameters for geometries as PGgeometry objects. With Hibernate 5 it receives these parameters as byte arrays and can only log a cryptic address like [B@1361cb3e).
We assume that this byte array is the reason for another problem we ran into by using the function buffer in JPQL statements:

Is it possible to enforce Hibernate to use PGgeometry objects instead of byte arrays? If not we would be interested why the behaviour was changed?

Kind regards,

Marko Skocibusic

I guess it's a mapping issue since Hibernate cannot resolve the type properly and it default to a byte array.

Did you add the hibernate-spatial dependency and are you using the PostgisPG9Dialect?

Hi Vlad,

thanks for your reply. We already have a dependency on hibernate spatial and use PostgisPG9Dialect. Furthermore I do not think that there is a problem with our mapping, as we do not have any problem with storing or loading our entities.

Kind regards,
Marko Skocibusic

Then, you should debug the Hibernate 4 and 5 versions and see why 4 is working and 5 is not. You should also provide a test case and attach it to a new Jira issue.

Thanks

Ok, I created an issue: HHH-11764.

Our problem is that Hibernate 4 bound JTS geometry parameters to the type PGgeometry and Hibernate 5 binds them to byte array.