[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-899?page=co...
]
Max Rydahl Andersen commented on HBX-899:
-----------------------------------------
If we add problems/warnings it should go into the Problem View; not a new one.
Note that namedqueries etc. already does this for syntax/compile errors.
But having the query validated inside the hql editor with a squiggly line sounds fair.
Make the HQL editor mimic the java editor better and problem view
-----------------------------------------------------------------
Key: HBX-899
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-899
Project: Hibernate Tools
Type: New Feature
Versions: 3.2beta8
Reporter: Joseph Marques
Instead of having to check the error log to see whether your query has an error, the
Tools should be smart enough to parse the query on the fly as it's being written.
This way the HQL editor can show the "little red squiggly" under the part of the
query that's in error. Additionally, the error log can then take a backseat to a new
"Query Problems" view that mimics the standard Problems view that showing
errors, warnings, info. An error could be a part of the query that doesn't make sense
while a warning could be the use of a reserved word as a bind parameter such as
":group" - which will work (I've tried it) - but is generally not a best
practice I would think.
--
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