persistence icon indicating copy to clipboard operation
persistence copied to clipboard

Add support to retrieve JPQL query from Query object

Open lukasj opened this issue 13 years ago • 9 comments

Currently the interfaces javax.persistence.criteria.AbstractQuery and javax.persistence.Query have no support for retrieving the underlying JPQL Query for additional transformation which would be, especially for named queries, very useful! Just think of the fact, that you currently have to copy and paste a named query if you like to have exactly the same query with an additional predicate in the where clause. The predicate in the where clause is just an example, there are probably tons of use cases where this feature would be helpful and minimize redundant code!

I would suggest to add the following methods:

**Query.java**public interface Query{
  // currently available methods... 
  public String getQuery();
}
**AbstractQuery.java**public interface AbstractQuery{
  // currently available methods... 
  public String getQuery();
}

lukasj avatar May 24 '12 19:05 lukasj

  • Issue Imported From: https://github.com/javaee/jpa-spec/issues/25
  • Original Issue Raised By:@glassfishrobot
  • Original Issue Assigned To: @ldemichiel

lukasj avatar Aug 31 '18 16:08 lukasj

@glassfishrobot Commented Reported by c.beikov

lukasj avatar May 24 '12 19:05 lukasj

@glassfishrobot Commented agoncal said: As I wrote on my blog (http://agoncal.wordpress.com/2012/05/24/how-to-get-the-jpqlsql-string-from-a-criteriaquery-in-jpa/), having the JPQL String representation of a CriteriaQuery is very useful for debugging purpose. And going further, having the SQL String would also be useful. I would go for :

public interface Query {

  public String getJPQLQuery();
  public String getSQLQuery();

}

lukasj avatar May 25 '12 08:05 lukasj

@glassfishrobot Commented @ldemichiel said: Being able to map back and forth between CriteriaQueries and JPQL queries would be useful to have. This is something that should be considered in a future release. See also http://java.net/jira/browse/JPA_SPEC-29

lukasj avatar Feb 22 '13 22:02 lukasj

@glassfishrobot Commented @arjantijms said: Just wondering if this is still considered, specifically for Java EE 8 (for which no JPA EG has been formed as of now).

In the 3 years since this issue has been created the lack of this feature impedes my work on almost a daily basis. In particular it makes paging/sorting from services quite difficult and obscure.

lukasj avatar Jun 22 '15 16:06 lukasj

@glassfishrobot Commented neilstockton said: +1 but I would suggest that the method to return the (SQL) native query is actually

String getNativeQuery();

which then aligns with how "SQL" is accessible in the query API.

lukasj avatar Jun 24 '15 12:06 lukasj

@glassfishrobot Commented @arjantijms said: I wrote an article about this issue and described how to do this when using Hibernate. See http://arjan-tijms.omnifaces.org/2012/06/counting-rows-returned-from-jpa-query.html

Ideally something like would be standardized. Note that just String getNativeQuery() is not really enough. Some info about the translated query parameters is also needed.

lukasj avatar Jun 25 '15 16:06 lukasj

@glassfishrobot Commented This issue was imported from java.net JIRA JPA_SPEC-25

lukasj avatar May 05 '17 06:05 lukasj

FWIW, returning the JPQL/HQL string could be easily implemented in Hibernate 6.0 as the AST model provides the option to render to an HQL string. If anyone is willing to work on this, Hibernate can serve as a compatible implementation.

beikov avatar Mar 18 '22 12:03 beikov