search

WilliamRen / django-pyodbc

Automatically exported from code.google.com/p/django-pyodbc
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Tested/working environments should be updated #26

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Personally, I have been successfully running django-pyodbc in the following
environments:

* Windows XP SP2
* Python 2.5.2
* Django 1.0

* Fedora Linux 8
* Python 2.5.1
* Django 1.0
* unixODBC 2.2.12
* FreeTDS 0.64

Both instances are pointing at:
* Windows Server 2003
* SQL Server 2000 SP4

Original issue reported on code.google.com by tarkatronic on 13 Nov 2008 at 4:30

GoogleCodeExporter commented 8 years ago 
What I like to propose is use our (new) test suite and/or the Django test suite 
as a
way to measure if a cliente -side stack can be called 'working', this is 
specially
true in  Unix/Mac OS X environments as in Windows only variable component is 
the 
ODBC driver.

Ideally, only django-pyodbc errors should be seen when running such tests.

Fortunately, currently there is a combination of (relatively recent) pieces of 
the 
Unix stack (FreeTDS, unixODBC, pyodbc) that provide exactly that (no failures 
imputable to these components when running the Django test suite), I have 
personally 
moved to using a Debian Linux system as the main development environment. I 
need to
document this in the wiki.

Original comment by cra...@gmail.com on 11 Jan 2009 at 2:46