JPA Criteria spatial extension #3819
Closed
beikov
started this conversation in
Design Proposals
Replies: 1 comment 5 replies
-
This should really be up to, or at least as significant imput from, Karel. I started this discussion with him yesterday on Zulip. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hibernate Spatial was not yet adapted in 6.0 and I would like to propose we try to move some code from the spatial module into hibernate-core. IMO the only reason for having a separate module is to avoid a dependency on the geometry type libraries, but we could move everything that is unrelated to the types up into hibernate-core.
My idea is that hibernate-spatial in 6.0 will only contain:
The JPA Criteria extensions could be made accessible through the existing
JTSSpatialPredicates
class with it's static methods, or through a subclassSpatialCriteriaBuilder
which could be created/accessed through aunwrap
method onHibernateCriteriaBuilder
. This could look like the following:The spatial criteria builder, and maybe other implementions (search, ogm), would be added to the HibernateCriteriaBuilder through a service loader contract. This could look like the following:
Beta Was this translation helpful? Give feedback.
All reactions