Re: [transfer-dev] Re: Non case sensitive searches, revisited SOLVED! ... for now
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 any discussion taken place about this? what is the best way to send you the changes? Thanks for your great work! 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 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
Re: [transfer-dev] Re: Non case sensitive searches, revisited SOLVED! ... for now
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 pe...@bezunartea.net 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 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 -- E: mark.man...@gmail.com T: http://www.twitter.com/neurotic W: www.compoundtheory.com cf.Objective(ANZ) + Flex - Nov 17, 18 - Melbourne Australia http://www.cfobjective.com.au 2 Devs from Down Under Podcast http://www.2ddu.com/ -- 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
[transfer-dev] Re: Non case sensitive searches, revisited
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
