Managing custom queries inside @query annotations has become unmanageable through QueryUtils. Simply put, a collection of regular expressions does not suffice. So we instead need to craft a JPQL-compliant parser that allows us to:
- Derive count queries
- Support sortable parameters
- supports standard JPQL
- possibly support HQL (Hibernate)
- possibly support EQL (EclipseLink)
At first, it should be based upon JPA 3.1, the standard Spring Data JPA 3.1 is aligned with. If there is an agreed-upon reason to implement backwards compatibility with older versions of JPA, we can evaluate that.
Managing custom queries inside @query annotations has become unmanageable through
QueryUtils. Simply put, a collection of regular expressions does not suffice. So we instead need to craft a JPQL-compliant parser that allows us to:At first, it should be based upon JPA 3.1, the standard Spring Data JPA 3.1 is aligned with. If there is an agreed-upon reason to implement backwards compatibility with older versions of JPA, we can evaluate that.