Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a JPQL parser #2814

Closed
gregturn opened this issue Feb 22, 2023 · 0 comments
Closed

Create a JPQL parser #2814

gregturn opened this issue Feb 22, 2023 · 0 comments
Assignees
Labels
in: query-parser Everything related to parsing JPQL or SQL type: enhancement A general enhancement

Comments

@gregturn
Copy link
Contributor

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.

@gregturn gregturn added type: enhancement A general enhancement in: query-parser Everything related to parsing JPQL or SQL labels Feb 22, 2023
@gregturn gregturn added this to the 3.1 M3 (2023.0.0) milestone Feb 22, 2023
@gregturn gregturn self-assigned this Feb 22, 2023
gregturn added a commit that referenced this issue Feb 22, 2023
gregturn added a commit that referenced this issue Feb 23, 2023
gregturn added a commit that referenced this issue Feb 24, 2023
gregturn added a commit that referenced this issue Feb 24, 2023
gregturn added a commit that referenced this issue Feb 24, 2023
Introduce a grammar that supports JPQL as defined by JPA 3.1 and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 1, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 2, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 2, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 2, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 2, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 3, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 3, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 6, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 6, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 6, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 6, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 6, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 6, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 7, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 7, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 8, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
gregturn added a commit that referenced this issue Mar 14, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: #2814.
klajdipaja pushed a commit to klajdipaja/spring-data-jpa that referenced this issue Mar 24, 2023
Introduce grammars that support both JPQL (JPA 3.1) as well as HQL (Hibernate 6.1) and allow us to leverage it for query handling.

Related: spring-projects#2814.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: query-parser Everything related to parsing JPQL or SQL type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant