[Posted this reply yesterday, but I can't see it, I post it again. Sorry for any duplication. / Ulf ]
On Jun 27, 4:12 pm, gordyt <[EMAIL PROTECTED]> wrote: > Ulf I haven't played with this second solution, but I did just check > out a copy of the django-pyodbc project. You should be OK following > the author's instructions. He said to add the django-pydobc directory > (where ever you choose to put it) to your PYTHONPATH. The name of the > module(s) that get imported do not have a "-" in them... they are > entities like contrib.admin.models and db.mssql. By adding django- > pydobc to your PYTHONPATH you are just giving Python another place to > look when importing stuff. Hi Gordon, thanks for your prompt answer. I would be very happy if I could get django-pyodbc working like the author states. Unfortunately, this does not seem to be the case for me. I've now started my installation process over again trying to follow the author's instructions, and here is what I did and the results: I installed the patched version (0.8.1) of pymssql (from https://sourceforge.net/tracker/index.php?func=detail&aid=1918448&group_id=40059&atid=426919) and placed it as pymssql.py in my site-packages directory. I downloaded the django-pyodbc package (revision 12) by doing: svn checkout http://django-pyodbc.googlecode.com/svn/trunk/ django- pyodbc-read-only as stated on the package website (http://code.google.com/p/django- pyodbc/source/checkout). Then I copied the subdirectory django-pyodbc to my site-packages directory. The next step is to added django-pyodbc to my PYTHONPATH. Since I'm running my web project under mod_python, I presume it has to be done in the httpd.conf file. So I added django-pyodbc to my path with the following line in httpd.conf: PythonPath "['/Users/ulf/web'] + ['/Library/Frameworks/ Python.framework/Versions/Current/lib/python2.5/site-packages/django- pyodbc'] + sys.path" and restarted Apache. (In my case: sudo /opt/local/etc/LaunchDaemons/ org.macports.apache2/apache2.wrapper restart) Then I changed my Django settings to the suggested: DATABASE_ENGINE = 'django-pyodbc.db.mssql' DATABASE_NAME = 'AdressRattning' DATABASE_USER = 'django' DATABASE_PASSWORD = '****' DATABASE_HOST = 'SQL_server_on_mac' DATABASE_PORT = '1433' and tried loading a database-accessing web page, and got the following error message: File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/ site-packages/django/db/__init__.py", line 24, in <module> backend = __import__('%s.base' % settings.DATABASE_ENGINE, {}, {}, ['']) ImportError: No module named django-pyodbc.db.mssql.base This is the not-so-helpful message I've seen a lot of times when trying to get external mssql modules working in Django. It emanates from a try-exception statement in django/db/__init__.py: # If the import failed, we might be looking for a database backend # distributed external to Django. So we'll try that next. try: _import_path = '' backend = __import__('%s.base' % settings.DATABASE_ENGINE, {}, {}, ['']) creation = __import__('%s.creation' % settings.DATABASE_ENGINE, {}, {}, ['']) except ImportError, e_user: raise # The database backend wasn't found. Display a helpful error message If something goes astray in the statement will raise an ImportError error stating that there is no module, which is not true; the module is there, but somehow misbehaving. I can actually see it being compiled to a base.pyc file, so I know it is being accessed. So, there is still something wrong with base.py, but how can I see what is going on, when the try-except statement in __init__.py is covering it? I try to import it directly in a Python interactive session: >>> import django-pyodbc.db.mssql.base File "<stdin>", line 1 import django-pyodbc.db.mssql.base ^ SyntaxError: invalid syntax and is back to the non-valid hyphenated module path... Furthermore, I can se a number of references to hyphenated modules in the __init__.py of django-pyodbc.db.mssql: # monkeypatching django from django.contrib.sessions.backends.db import SessionStore from django-pyodbc.contrib.sessions.backends.db import SessionStore as NewSessionStore from django-pyodbc.db.models.base import Model from django-pyodbc.db.models.base import Model as NewModel import django.models.fields import django-pyodbc.models.fields from django.models.fields import TimeField, Field, DateTimeField from django-pyodbc.models.fields import TimeField as NewTimeField, Field as NewField, DateTimeField as NewDateTimeField from django.test.utils import _set_autocommit from django.pyodbc.test.utils import _set_autocommitNew from django.contrib.admin.models import LogEntry from django-pyodbc.contrib.admin.models import LogEntry as NewLogEntry If I try to run __init__.py I get this message: File "__init__.py", line 3 from django-pyodbc.contrib.sessions.backends.db import SessionStore as NewSessionStore ^ SyntaxError: invalid syntax So, my initial question still remains: Is there anyone around here that has django-pyodbc running, and if so; how did you do it? Thanks for any further help on this, Ulf --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
