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/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to