Django with SQL Server

[kellygreer1]

I'm trying to get Django working on Windows with Apache and MS SQL
Server.

I have completed.
1) Install Apache
2) Install Python 2.5
3) Install mod_python and configure
4) Install Django
5) Setup test project
-- here I learn my Python install is going to need a
-- few more things If I'm going to use SQL Server
6) Install PDO-1.3.2
7) Install pywin
8) Install adodbapi-2.1

refresh the root URL of my test project and "bam"... error
The traceback is below my sig. Any ideas on how to solve this?

Kelly Greer
kelly...@nospam.com
change nospam to yahoo

Traceback (most recent call last):

File "C:\Python25\lib\site-packages\mod_python\importer.py", line
1537, in HandlerDispatch
default=default_handler, arg=req, silent=hlist.silent)

File "C:\Python25\lib\site-packages\mod_python\importer.py", line
1229, in _process_target
result = _execute_target(config, req, object, arg)

File "C:\Python25\lib\site-packages\mod_python\importer.py", line
1128, in _execute_target
result = object(arg)

File "C:\Python25\lib\site-packages\django\core\handlers
\modpython.py", line 177, in handler
return ModPythonHandler()(req)

File "C:\Python25\lib\site-packages\django\core\handlers
\modpython.py", line 145, in __call__
self.load_middleware()

File "C:\Python25\lib\site-packages\django\core\handlers\base.py",
line 29, in load_middleware
mod = __import__(mw_module, {}, {}, [''])

File "C:\Python25\lib\site-packages\django\contrib\sessions
\middleware.py", line 2, in <module>
from django.contrib.sessions.models import Session

File "C:\Python25\lib\site-packages\django\contrib\sessions
\models.py", line 3, in <module>
from django.db import models

File "C:\Python25\lib\site-packages\django\db\__init__.py", line 11,
in <module>
backend = __import__('django.db.backends.%s.base' %
settings.DATABASE_ENGINE, {}, {}, [''])

File "C:\Python25\lib\site-packages\django\db\backends\ado_mssql
\base.py", line 12, in <module>
raise ImproperlyConfigured, "Error loading adodbapi module: %s" %
e

ImproperlyConfigured: Error loading adodbapi module: No module named
System

[kellygreer1]

OK made it a bit farther. After all that I restarted Apache.
Then refreshed my URL

http://someserver:8080/testproject

And I get the error ..
ImportError at /testproject/
No module named testproject.urls
Request Method: GET
Request URL: http://someserver:8080/testproject/
Exception Type: ImportError
Exception Value: No module named testproject.urls
Exception Location: C:\Python25\lib\site-packages\django\core
\urlresolvers.py in _get_urlconf_module, line 177

Any ideas?

Not sure if this matters but I had to use this in my httpd.conf to get
this far
SetEnv DJANGO_SETTINGS_MODULE settings
#instead of
SetEnv DJANGO_SETTINGS_MODULE testproject.settings

Thanks,
Kelly

On Mar 24, 6:41 pm, kellygreer1 <kellygre...@yahoo.com> wrote:
> I'm trying to get Django working on Windows with Apache and MS SQL
> Server.
>
> I have completed.
> 1) Install Apache
> 2) Install Python 2.5
> 3) Install mod_python and configure
> 4) Install Django
> 5) Setup test project
> -- here I learn my Python install is going to need a
> -- few more things If I'm going to use SQL Server
> 6) Install PDO-1.3.2
> 7) Install pywin
> 8) Install adodbapi-2.1
>
> refresh the root URL of my test project and "bam"... error
> The traceback is below my sig.  Any ideas on how to solve this?
>
> Kelly Greer

> kellygre...@nospam.com

[kellygreer1]

Hopefully this will help someone else.

# I changed this
<Location "/testproject/">
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE settings
PythonDebug On
PythonPath "['E:/htdocs/testproject'] + sys.path"
</Location>

# Into the text below and then it worked
<Location "/testproject/">
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE testproject.settings
PythonDebug On
PythonPath "['E:/htdocs'] + sys.path"
</Location>

Up and running now... Yeah!

Kelly

> > System- Hide quoted text -
>
> - Show quoted text -

[Malcolm Tredinnick]

On Mon, 2008-03-24 at 15:57 -0700, kellygreer1 wrote:
> Hopefully this will help someone else.
>
> # I changed this
> <Location "/testproject/">
> SetHandler python-program
> PythonHandler django.core.handlers.modpython
> SetEnv DJANGO_SETTINGS_MODULE settings
> PythonDebug On
> PythonPath "['E:/htdocs/testproject'] + sys.path"
> </Location>
>
> # Into the text below and then it worked
> <Location "/testproject/">
> SetHandler python-program
> PythonHandler django.core.handlers.modpython
> SetEnv DJANGO_SETTINGS_MODULE testproject.settings
> PythonDebug On
> PythonPath "['E:/htdocs'] + sys.path"
> </Location>
>
> Up and running now... Yeah!

Something to be aware of: the adosql backend that comes with Django's
source is essentially unsupported and doesn't work in a few ways (there
are known bugs and, no doubt, unknown bugs). In fact, I suspect we're
pretty close to just removing the source of it from the tree to prevent
future confusion. It's impossible for us to maintain it as effectively
as the supported backends. Maintaining closed-source, proprietary
backends that run on only one company's operating system are a *lot*
harder than for open source databases that run everywhere (we have a
dedicated team of maintainers for the Oracle branch who had to prove
themselves before it was permitted into the main tree) and the person
who originally convinced us to commit this backend hasn't hung around,
so we've learnt the lesson there.

Instead, we are encouraging the various people who have put their hand
up to say "I'll work on it" to maintain it as an external backend
(database backends don't have to be part of Django's core these days),
but, as far as I'm aware nobody's gotten that far. There's an empty
Google code project (django-mssql, no source), but that seems to be a
solo effort.

Maybe search around Google or look in Trac to find the names of the
people who were interested in working on this, or maybe somebody on this
list know more. Trac tickets about MS SQL server are being closed with a
request to develop it externally, so searching for closed tickets with
SQL Server in the description will be a starting point.

So that's going to be a bit of a downer in your experiments with Django,
but I wanted to make sure you knew what you were getting into. Maybe
bits of it will work. We haven't made that many changes over the last
year or so. But it's not being actively maintained in trunk, so there
will be bugs.

Regards,
Malcolm

--
Experience is something you don't get until just after you need it.
http://www.pointy-stick.com/blog/

[Michael]

Hope this keeps working for you. For what it's worth, I couldn't get
SQLServer to work with Django a while back ... though our using
SQLServer 2000 might be a big part of that.

However, I was reading some PyCon blogs and came across a <a
href="http://jjinux.blogspot.com/2008/03/pycon-ironpython-road-
ahead.html">JJinuxLand</a> post that summarized an IronPython talk by
Jim Huninin. It had a couple lines:

IronPython makes it really easy to use SQLServer.
He (Jim Huginin) showed Django running under IronPython with only
minimal patching necessary.

Those are separate statements in the blog and that doesn't necessarily
mean IronPython can make Django work with SQLServer, but depending on
how your current path works out that might be another avenue to try.

[Michael]

Bad link, obviously ... http://jjinux.blogspot.com/2008/03/pycon-ironpython-road-ahead.html

[Adam V.]

Not only is Django's pack-in MS Sql backend broken, but the last set
of updates to adodbapi-2.1 to add IronPython support actually broke
standard Win32/COM support in some areas.

There are some now externally maintained SQL Server backends for
(trunk) Django:
* http://code.google.com/p/django-mssql/
* http://code.google.com/p/django-pyodbc/

I haven't tried the second one.

The first one, django-mssql, I "maintain", though that's perhaps too
strong a word since it's based on some previous user-provided patches.
(django-mssql packs its own internal (fixed) copy of adodbapi, so that
dependency is removed.)

If you do try that code, by all means submit bug reports and feature
requests at Google Code.

On Mar 24, 6:41 pm, kellygreer1 <kellygre...@yahoo.com> wrote:

> I'm trying to get Django working on Windows with Apache and MS SQL

> Server....

[kellygreer1]

I made it pretty far but now have run into this error trying to get
the admin interface up.


DatabaseError:
--ADODBAPI
-- Trying parameter 0 = '25354001e197c91af0f7fa63ab4b720d'

Traceback (most recent call last):

File "C:\Python25\Lib\site-packages\adodbapi\adodbapi.py", line
618, in _executeHelper
p=self.cmd.Parameters(parmIndx)
File "C:\Python25\lib\site-packages\win32com\client\dynamic.py",
line 172, in __call__
return
self._get_good_object_(self._oleobj_.Invoke(*allArgs),self._olerepr_.defaultDispatchName,None)
com_error: (-2147352567, 'Exception occurred.', (0,
'ADODB.Parameters', 'Item cannot be found in the collection
corresponding to the requested name or ordinal.', 'C:\\WINDOWS\\HELP\
\ADO270.CHM', 1240649, -2146825023), None)
-- on command: "SELECT [django_session].[session_key],[django_session].
[session_data],[django_session].[expire_date] FROM [django_session]
WHERE ([django_session].[session_key] = %s)"
-- with parameters: ['25354001e197c91af0f7fa63ab4b720d']

Any ideas?

Should I go ahead and swap the backend code out for of these backends?
How badly broken is the MS SQL support?
Hopefully I'll have my Django book from Amazon later today. I'm
flying blind right now.

Kelly

On Mar 25, 12:04 pm, "Adam V." <fla...@gmail.com> wrote:
> Not only is Django's pack-in MS Sql backend broken, but the last set
> of updates to adodbapi-2.1 to add IronPython support actually broke
> standard Win32/COM support in some areas.
>
> There are some now externally maintained SQL Server backends for
> (trunk) Django:
> *http://code.google.com/p/django-mssql/

> *http://code.google.com/p/django-pyodbc/

>
> I haven't tried the second one.
>
> The first one, django-mssql, I "maintain", though that's perhaps too
> strong a word since it's based on some previous user-provided patches.
> (django-mssql packs its own internal (fixed) copy of adodbapi, so that
> dependency is removed.)
>
> If you do try that code, by all means submit bug reports and feature
> requests at Google Code.
>
> On Mar 24, 6:41 pm, kellygreer1 <kellygre...@yahoo.com> wrote:
>
>
>
> > I'm trying to get Django working on Windows with Apache and MS SQL

> > Server....- Hide quoted text -

[Adam V.]

> Should I go ahead and swap the backend code out for of these backends?

The fact that I created a separate project basically speaks to my
suggestion (swap out.)

[I would kind of prefer if MS SQL support was dropped entirely from
django-svn (unless the upcoming foundation is going to spend some
money on Windows+SS support in the future?)]

[kellygreer1]

I realize this is a Django group but...
where do other Python web app frameworks like Pylons and TurboGears
stack up as far as MS SQL Server support goes?

I'll post back to the group my experiences of trying to swap out the
backend.
I'm a newb and swamped at work right now. So this may take me a few
days to get back to you.

Thanks for all the help,
Kelly