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 ( operatorClause | isNullClause |
inClause );
to
conditionBasicClause : PROPERTY_IDENTIFIER ( operatorClause |
likeOperatorClause | isNullClause | inClause );
...
likeOperatorClause : LIKE (MAPPED_PARAM | PROPERTY_IDENTIFIER);
LIKE : 'like';
and redefined OPERATOR to:
OPERATOR : ('='|'>'|'<'|'!='|'<>'|'>='|'<=') {
setMode(PROPERTY_IDENTIFIER_MODE); };
I can run the tests fine, but only get up to the Tree. So my questions are:
where does the SQL generation occur? I'd assumed it was all ANTLR based, but
I now see that the final Tree to SQL is be done in coldfusion code. Any
pointers, please?
Pedro.
PS: if you are interested on how ANTLR works, check the video tutorials done
by Scott Stanchfield, really well done:
http://javadude.com/articles/antlr3xtut/
--
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 transfer-dev@googlegroups.com
To unsubscribe from this group, send email to
transfer-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/transfer-dev?hl=en
