On Nov 6, 4:52 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote: > I don't get the near-desperate attempts to avoid SQL under all circumstances > that some people seem to fall in love to the very moment the start using a > ORM tool. The solution is easily expressed in a single query - why do you > strive for a different way to do it? Especially, when you know that in the > end, SQL will be the result anyway - after all, you are using an ORM mapper.
To be fair, I think the original poster was just trying to find a solution to a problem, and both the ORM tool and the "use it in the way it was intended" type of replies tend to channel you down that sort of route. Obviously your first instinct is to try and see if the tool provides a clean and native way to do what you want, since you don't need an explicit select for most other uses. Personally I sometimes appreciate the benefits something like SQLObject gives me, and other times curse the obfuscation it causes. The very first join I tried to do with my latest TurboGears project failed with a cryptic error because the User table actually uses the identifier tg_user and therefore the default join condition fails spectacularly. So you inevitably just end up digging through the database to work out what on earth the mapper actually did in the first place! :) -- Ben Sizer --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
