#11329: get_count generates incorrect SQL for query sets with extra 'select' and
'where'
-------------------------------------------------------+--------------------
 Reporter:  bogklug                                    |       Owner:  nobody   
 
   Status:  new                                        |   Milestone:           
 
Component:  Database layer (models, ORM)               |     Version:  1.0      
 
 Keywords:  sql, extra select, extra where, get_count  |       Stage:  
Unreviewed
Has_patch:  0                                          |  
-------------------------------------------------------+--------------------
 Extending an example on extra 'select' from
 http://docs.djangoproject.com/en/1.0/ref/models/querysets/ with an extra
 'with' and calling get_count:

 Blog.objects.extra(
     select={
         'entry_count': 'SELECT COUNT(*) FROM blog_entry WHERE
 blog_entry.blog_id = blog_blog.id'
     },
     where=['entry_count=0']
 ).query.get_count()

 results in OperationalError: no such column: entry_count.

 The SQL for the query itself is ok. It seems that the problem is caused by
 get_count.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/11329>
Django <http://code.djangoproject.com/>
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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to