I've run into a problem that appears to be caused by multiple django
versions running on the same server. I have a preforked mod_python
installation and the problem I'm seeing is this: after using the trunk-
based application, I try to use the 0.91-based application and get a
500 error. The root of the SQL error is that variables aren't quoted
properly and it can't find a column name, which you can see if you
look at the SQL that is printed out. Here's an example of the error:
ERROR: column "activity" does not exist SELECT
"packages"."label","packages"."name" FROM "packages" WHERE
"packages"."label" = activity ORDER BY "packages"."name" ASC
Looking at the variables, the params list contains a unicode variable
- which I don't think will work okay in 0.91:
params [u'activity']
The error occurs only after I have visited the trunk-based
application. If I restart the server, I can use the 0.91-based
application continuously. Looking in log files I have seen that the
500 error occurs after somebody has used the trunk-based application,
plus the error has only showed up after I deployed the trunk-based
application in the last week or so. I thought this problem would be
avoided by using the PythonInterpreter option, but it hasn't worked so
far. Here are my Location directives from my testing server (which
also reproduces the problem):
<Location "/santacruz">
SetHandler mod_python
PythonPath "['/opt/djangolibs/django_src','/djangoapps'] +
sys.path"
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE sc_ca.settings
PythonInterpreter sc_ca
PythonDebug On
SSLRequireSSL
</Location>
<Location "/curriculum">
SetHandler mod_python
PythonPath "['/opt/djangolibs/django_trunk','/djangoapps'] +
sys.path"
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE syb.noisy.settings
PythonInterpreter curriculum
PythonDebug On
SSLRequireSSL
</Location>
The directories django_src is the 0.91 tree, django_trunk is obviously
trunk, and I don't have a link to either in site-packages. I've
removed *.pyc files in all the trees but this only delays the problem
until the files are regenerated.
Please, if you've seen the same issue or have any helpful ideas to try
to stop the error, let me know.
Thanks!
-rob
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
