Thank you for your replies.
> The problem is that the filter you specified was not returning the
> correct answer in 0.96. You're asking that Django returns an incorrect
> result to make your code faster. It's possible to give incorrect results
> very fast, but it's not something we want to suppo
Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Wed, 2008-07-16 at 10:12 -0700, serbaut wrote:
> > Consider the following equivalent queries based on the weblog model
> > from the documentation:
>
> > Blog.objects.filter(name="myblog").exclude(entry__body_text__contains=&q
Consider the following equivalent queries based on the weblog model
from the documentation:
Blog.objects.filter(name="myblog").exclude(entry__body_text__contains="blah
blah")
Blog.objects.filter(Q(name="myblog") &
QNot(Q(entry__body_text__contains="blah blah"))) # 0.96
Blog.objects.filter(Q(name=
Ok, thank you for the answer. I am using newforms with an older django
codebase so thats why I ran into this.
On Jan 9, 3:38 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> On 1/9/07, serbaut <[EMAIL PROTECTED]> wrote:
>
> > fields.py tries to get sett
fields.py tries to get settings.URL_VALIDATOR_USER_AGENT with:
try:
from django.conf import settings
URL_VALIDATOR_USER_AGENT = settings.URL_VALIDATOR_USER_AGENT
except ImportError:
# It's OK if Django settings aren't configured.
URL_VALIDATOR_USER_AGENT = 'Django (http://www.djan
> Judging from the comments on that ticket, I think it's a slightly
> different issue; #2210 deals with fetching the Options class of the
> wrong model when the related field has 'db_column' set; in that case,
> it appears Django is generating the correct table list for the query,
> but not the co
I submitted a patch for this a while back:
http://code.djangoproject.com/attachment/ticket/2210/order_by_related.diff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this grou
