Re: Inconsistent keyword filtering on FK

2011-06-23 Thread Ethan Miller

On Jun 23, 2011, at 2:30 PM, Ian Clelland wrote:

> person_id is a column in the payee table, and Django will construct SQL which 
> compares against that.

It's the reverse actually payee_id is a column on the person table so I 
guess the resulting SQL would need to be 

select * from er_payee, er_person where er_person.id = 26 and 
er_person.payee_id = er_payee.id;

or

select * from er_payee join er_person on er_person.id = 26 and 
er_person.payee_id = er_payee.id;

? In any case it's not getting that far - seems like it fails before it even 
builds a query ...

-- 
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.



Re: Inconsistent keyword filtering on FK

2011-06-23 Thread Ethan Miller

On Jun 23, 2011, at 2:21 PM, Cal Leeming [Simplicity Media Ltd] wrote:

> Payee.objects.filter(
> person = Person(id=26)
> )
> 
> or.. Payee.objects.filter(
> person__id = 26
> ) 

Both of these return the same error - it lists out all the "choices" which are 
all fields on the payee table itself (and the one I mentioned that appears in 
the cache)

-- 
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.



Re: Disabling python-caching with mod_python, Apache 2.2

2007-08-13 Thread Ethan Miller

On 8/13/07 10:55 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:

> However, it seems like the requested pages are cached. Not in the
> regular way though, it is as though the compiled Python procedures are
> compiled, while the data is still up to date.
> 
> I'm wondering if this is a problem with mod_python and does anyone
> know how to turn this "python-caching" off?

Check this section:
http://www.djangoproject.com/documentation/modpython/#running-a-development-
server-with-mod-python

If you don't have enough privileges to restart or configure Apache (like me
on a dreamhost acct) you can also kill your python process 'pkill python'

- Ethan


--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---