I should also add that the changes posted support TQL queries with the format "Object.Property LIKE :param", and not ":param LIKE Object.Property".
Now that I better understand how antlrTQL works, I'd like to add support for SQL functions that only require one argument: LOWER(), UPPER() and the like. The plan is: - Modify the TQL grammar to support this kind of functions and pass them through the parser untouched. - Adapt transfer coldfusion code to ignore these functions, and also leave them untouched. The question is, how should I approach changes in the coldfusion code? Or better yet, do I really need to adapt the coldfusion code? If the output from antlrTQL is already proper SQL I might not need to modify it at all. Any comments? Pedro. -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en
