Comments on: When Does an HQL Typo *Not* Cause A Parse Error? http://joeygibson.com/2008/09/26/when-does-an-hql-typo-not-cause-a-parse-error/ Java, Clojure, Scala, Groovy, Ruby, Python, Lisp, Objective-C, OSX, politics, religion, Koine Greek, Tae Kwon Do, Spanish and much more! Fri, 27 Jan 2012 16:22:41 +0000 hourly 1 http://wordpress.org/?v= By: joeygibson http://joeygibson.com/2008/09/26/when-does-an-hql-typo-not-cause-a-parse-error/comment-page-1/#comment-546 joeygibson Fri, 26 Sep 2008 15:48:52 +0000 http://joeygibson.com/?p=809#comment-546 This query was actually embedded in a String, so Eclipse wasn't able to colorize it for us. Once I pasted the query into a view inside Hibernate Tools, it was easy to spot. This query was actually embedded in a String, so Eclipse wasn’t able to colorize it for us. Once I pasted the query into a view inside Hibernate Tools, it was easy to spot.

]]> By: Seth http://joeygibson.com/2008/09/26/when-does-an-hql-typo-not-cause-a-parse-error/comment-page-1/#comment-545 Seth Fri, 26 Sep 2008 15:10:42 +0000 http://joeygibson.com/?p=809#comment-545 You must not be using an editor that has syntax coloring...? That would have made this typo a lot easier to spot, because "left" would be colored as a keyword but "lef" would not. That's the biggest benefit of syntax coloring, imo. (This coming from someone who writes language support modules in text editors, for a living...) :-) You must not be using an editor that has syntax coloring…? That would have made this typo a lot easier to spot, because “left” would be colored as a keyword but “lef” would not.

That’s the biggest benefit of syntax coloring, imo. (This coming from someone who writes language support modules in text editors, for a living…)

:-)

]]>