[hibernate-issues] [Hibernate-JIRA] Created: (HBX-878) Support comment-naming of tabs in the Hibernate Query Result view

Support comment-naming of tabs in the Hibernate Query Result view ----------------------------------------------------------------- Key: HBX-878 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-878 Project: Hibernate Tools Type: New Feature Versions: 3.2beta8 Reporter: Joseph Marques Let's pretend some long query looks like this: "select a from A a inner join a.bs b inner join b.cs c where b.nested.prop = :bval and c.nested.prop = :cval" When I execute this query a tab is created in the Hibernate Query Result view with the title equal to the entire query itself. I propose that the HQL editor allow some simple form of comments above the query, which will then act as logic name for the tab. In other words: // A.getAsByComplexBCSubselect "select a from A a inner join a.bs b inner join b.cs c where b.nested.prop = :bval and c.nested.prop = :cval" Then, if the user highlights both of these lines, he is intentioning that he wants the tab to be named by using the contents in the first line comment. And if the first line isn't a comment, well then you could always default back to the classic functionality of putting the entire query into the tab title. Optionally, if the user doesn't have a specific name for it, but still doesn't want a tab that spans the entire length of the IDE, he could use something like: // "select a from A a inner join a.bs b inner join b.cs c where b.nested.prop = :bval and c.nested.prop = :cval" to intimate that he wants the tab to show up as something short. It could be as simple as "unnamed1", "unnamed2", "unnamed3", etc, just as long as it's short and sweet and allows for more than one tab title to be seen simultaneously for long queries. -- 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