[hibernate-issues] [Hibernate-JIRA] Commented: (HBX-896) Support multi-query HQL editor environment

[Joseph Marques (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-896?page=comments#action_26232 ] 

Joseph Marques commented on HBX-896:
------------------------------------

In fact, instead of highlight-run there's a more user-friendly solution.  Just position the cursor in any part of the desired query section (boundaries denoted by the use of separating comments), and click run.

If the cursor is inside a comment (or perhaps on the same line as a comment, if they are to be line comments instead of block comments [supporting both would be great]), then the execute function should be disabled.  In other words, the execute functionality then becomes contingent on where the cursor is.

However, I think think that there is a benefit to the highlight-run strategy, because it would allow sub-portions of queries to be selected and run independently.  One great use case for this would be to highlight-run a sub-select, to see if it returns the correct sub-results, and if it does to then run the entire query because I know the sub-select is perfect.

> Support multi-query HQL editor environment
> ------------------------------------------
>
>          Key: HBX-896
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-896
>      Project: Hibernate Tools
>         Type: New Feature

>     Versions: 3.2beta8
>     Reporter: Joseph Marques
>  Attachments: hqlSnippet.png
>
>
> Allow multiple select statements in the HQL editor.
> Then a user could:
> * highlight-run the desired query, or
> * click-run, to run all of the queries
> The different sections could be seperated by some special character or phrase, say, "--" (two dashed), to signify that lexing should begin anew after the special character.
> Even better, the editor could support user-comments above the start of each query.  It would be optional above the first one (so that the HQL editor can be used identically to how it used to when it only worked for single queries), but required for any other queries in the same editor.  This way, the lexar still knows when to break and start over.  (see attachedment)

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira