It seems TQL can only accomodate "basic" (at least to me) SQL which makes it feels like I'm going backwards.
You can't use built-in DB functions (at least that's how I understand it reading the TQL doc page). We use oracle here and there are many useful functions built-in the DB. 1. why would you use TQL over standard SQL (which every programmer would know)? The 2. maybe there are tips/tricks available to make TQL more flexible? if yes, please tell me. 3. Also is there any reason to use an transfer object vs standard query datatype when retrieving data? I think transfer as a whole is very useful. But there are points in my current project where I begin to wonder if TQL is constricting my freedom when it comes in retrieving data. Thank you very much :) --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer 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 -~----------~----~----~----~------~----~------~--~---
