[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co... ] Steve Ebersole commented on HHH-530: ------------------------------------ I am looking at it as well. For this and for other reasons as well, I think a much better solution is to simply embed the parameters into the HQL AST tree and have them "pull" their values from QueryParameters (currently the values are "pushed" from QueryParameters by Loader). This has benefits in many use-cases. There is a trade-off in this approach in that after parsing and translation we must collect the query parameters (the ParameterSpecifications) in order to iterate them for binding. Not sure yet of the performance impact of that change. Another option that would perform much better would be to collect the ParameterSpecifications during sql.g processing. This later option is what I intend for later. Just not sure how feasible it is given the mix of AST and JoinFragment/JoinSequences currently in the HQL translator. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira