TQL is db agnostic so it is guaranteed to be portable across databses. Also it references names in your object model, not the db names, so there is more consistency.
With that said, at one point or another you will have to use straight SQL, and there is nothing wrong with that. We all do it. Some queries are just too complex and some queries don't need to be stuffed in an object model. Don't feel like you are breaking the code of the secret society if you do. Baz On Wed, Jun 24, 2009 at 12:51 AM, jarthel <[email protected]> wrote: > > I forgot to say that my "framework" is something like > > service (includes crud) -> gateway -> TQL. > > I'm not sure if this is relevant to my original message but I'll > include it anyway. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
