#2348: Unbound local error when performing invalid query
------------------------------+---------------------------------------------
 Reporter:  [EMAIL PROTECTED]   |        Owner:  adrian
     Type:  defect            |       Status:  new   
 Priority:  normal            |    Milestone:        
Component:  Database wrapper  |      Version:  SVN   
 Severity:  minor             |   Resolution:        
 Keywords:                    |  
------------------------------+---------------------------------------------
Comment (by mtredinnick):

 This error won't ever be able to be reported as "invalid query type",
 because the lack of an invalid type just means we assume you have not
 specified one and append {{{__exact}}} to the end ("exact" is implied if
 nothing is given). The syntax you are using is valid for looking up the
 "equals" field in the related "name" model.
 
 I suspect the actual error here is being caused by the same thing as #2287
 (i.e. it's not clear why we are getting that far into the code). We can do
 a bit better in the error message, I suspect. This will need to wait until
 the current refactoring in django.db.model is completed, though.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/2348>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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/django-updates
-~----------~----~----~----~------~----~------~--~---

Reply via email to