SQL Server

15 views
Skip to first unread message

Mike Kenny

unread,
Apr 15, 2011, 10:00:55 AM4/15/11
to Django users
Hi,

I am trying to use a django application developed on Linux with MySQL
on a Windows box with SQL Server. I have downloaded pyodbc and set my
ENGINE to sql_server.pyodbc (and tried just pyodbc as I was able to
import this into python but not sql_server). Both result in an error
message listing the supported engines, of which pyodbc is not listed.

Obviously I have missed a step somewhere, does anybody know hat it
might be? Or can somebody provide me with an idiot's guide to using
django with SQL Server. (Unfortunately I am not at home in a windows
environment)

The software I am using is python 2.7 ,django 1.3 and pyodbc 2.18

Thanks,

mike

Jirka Vejrazka

unread,
Apr 15, 2011, 10:25:26 AM4/15/11
to django...@googlegroups.com
Mike,

I use exactly the same setup. Look up the "django-odbc" package.
This will be quite easy to use and setup, but there are some
unresolved bugs in that package related to multi-db support. Most of
them have patches attached to their tickets.

Cheers

Jirka

> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

Javier Guerra Giraldez

unread,
Apr 15, 2011, 10:38:09 AM4/15/11
to django...@googlegroups.com
On Fri, Apr 15, 2011 at 9:25 AM, Jirka Vejrazka
<jirka.v...@gmail.com> wrote:
>  I use exactly the same setup. Look up the "django-odbc" package.
> This will be quite easy to use and setup, but there are some
> unresolved bugs in that package related to multi-db support. Most of
> them have patches attached to their tickets.

i tried django-odbc recently but got frustrated because of problems in
the utf8-latin1 mismatches. i think it has something to do with the
exact versions of the unix-odbc layer and the MSSQL server, and also
because the existing database was 'designed' without any thoughts for
character encoding (people here are used 'forgive' computers for
mangling accents and ñ)

in the end i used django's ORM for my own databases and straight SQL
(via pyodbc) for MSSQL access.

--
Javier

Reply all
Reply to author
Forward
0 new messages