[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-897?page=co... ] Joseph Marques commented on HBX-897: ------------------------------------ As an alternate strategy, you can add an additional column the the query parameters view, say, "Query". This column would map back to the name of the query (a.k.a the comment that precedes each query). This way, each query in the multi-query environment could have it's own parameter, just in case they use the same binding in the JPQL/HQL but want to pass different values. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-897?page=co... ] Joseph Marques commented on HBX-897: ------------------------------------ "eed to know which parameters are actually needed upfront" -> but then how do you generate the list of needed parameters when you click that ":p-with-a-plus-sign" icon? I figured you actually pulled it from the query, but maybe you just generically scan the editor area looking for tokens that start with a colon? Hmm...interesting. So as the cursor moves through the different statements in the edtior (perhaps now seperated by semi-colons [see HBX-896]) the list of parameters would change to the saved list for the given query? If so, that seems cool, but it doesn't allow you to have a global picture of things. The whole reason I want the HQL editor to support multiple queries was because - even in my short time using the tools - I hate flipping back and forth between 2, 3, or even 4 different editors when I'm mocking up new statements. Perhaps instead of another column (I totally understand the real estate issue), you could somehow use vertical separators (see HBX-901 attachments). Each distinct group of queries could have a "title row" that would distinguish it's block of parameters from the others (I'm thinking in terms of html, but something like a colspan across name / type / value / null). -- 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