On Mon, May 25, 2009 at 8:19 AM, Bobby Roberts <tchend...@gmail.com> wrote:
> > > If you take a look at Q objects they allow you to do just that: > http://docs.djangoproject.com/en/dev/topics/db/queries/#complex-looku... > > > > Alex > > Hi Alex... that might take some reading up on and time is short at the > moment. I just found the pipe delimiter in filters so: > > pg=WebPage.objects.filter(body__icontains=delurl) | > WebPage.objects.filter(blurb__icontains=delurl) > > > works fine for what i need. I do have a question though since i'm > wanting to write the most efficient system possible in django. What > is the difference between this method and using a Q object? > > Thanks for your input! > > > For a case like this they probably result in roughly the same (if not identical) SQL. In general it's better to use Q objects since django doens't have to piece together 2 seperate cases and then munge them together, which can get difficult with complicated aliasing and probably can produce suboptimal SQL in those cases. Alexx -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
