This comes up every once in a while, and every once in a while I post a
link to my solution to this issue from a while back:
http://code.djangoproject.com/ticket/1007
This patch, while it might need some small tweaks to work against
recent trunks, lets you essentially turn this behavior off for specific
objects, while retaining some of the behavior where it is desired.
Hope it helps! I won't dig into the greater issue because James is
doing a great job of that himself (and, uh, I just woke up :)) but I
wanted y'all to know that there IS a stopgap solution and has been for
some time.
Regards,
Jeff
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
