I second Simon on that -- it's still light years ahead of spaghetti code! =)
On 7/19/06, Simon Willison <[EMAIL PROTECTED]> wrote: > > > On 19 Jul 2006, at 13:50, Maciej Bliziñski wrote: > > > is it possible to make the same thing without writing custom SQL code? > > No it isn't - but that's fine, that's exactly why Django allows (and > encourages) you to roll your own SQL when you need to: > > http://www.djangoproject.com/documentation/model_api/#executing- > custom-sql > > My philosophy with respect to the Django ORM (and ORMs in general) is > that it should be used strictly for convenience - it should make the > usual dull collection of queries as simple as possible. If the ORM is > ever less convenient than writing a raw SQL query, write a raw SQL > query! > > As long as you keep all of the SQL interactions in your Django model > classes your database logic will all be in the same place and > maintenance should be simple. > > Cheers, > > Simon > > > -- Carlos Yoder http://carlitosyoder.blogspot.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
