Thanks for the tip Mark, glad to hear from you again!
One question though, I remember checking the feature requests list somewhere
and this was already in. I haven't noticed any updates for quite a while,
and I don't know what the plan is (it's been working perfectly since v1.1) .
Anyway, has
I think you will need to adapt the CF code, as it's the one that walks the
AST that ANTLR generates.
Mark
2011/9/1 Pedro Bezunartea López
>
> I should also add that the changes posted support TQL queries with the
> format "Object.Property LIKE :param", and not ":param LIKE Object.Property".
>
>
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
I finally ended up modifying the component
transfer/com/tql/SelectStatement.cfc. I modified the method
executeEvaluation, these are the changes:
- added a local var:
- replaced the line 180 (#block.preSQL#) with:
#ReReplace( block.preSQL, "(.*) ([a-zA-Z_\.]+) LIKE$", "\1 LOWER(\2) LI
I have researched quite a bit about ANTLR, and I have now a clear idea what
needs to be done to the TQL lexer and parser. This is what I've done:
- in the file where TQL grammar is defined tql-20070315163054.jar, I
modified the file Tql.g, from:
conditionBasicClause : PROPERTY_IDENTIFIER ( opera
