On Fri, Sep 25, 2009 at 12:52:09PM -0600, Jeff Hardy wrote: >Hi Vernon, >I presume you're talking django-mssql >(http://code.google.com/p/django-mssql/)? I always wondered why it had >its own database layer.
Did you see there's some discussion now the issues of the project? Not particularly much, but http://code.google.com/p/django-mssql/issues/detail?id=68 >I don't think adodbapi is the best place to have django (or any other >ORM) specific stuff. django-mssql shoul talk to your module, and then >it should (in theory!) get IronPython support for free once you add >it. Maybe see what the django-mssql guys think about that? If adodbapi >is part of pywin32 (right?), I would think that depending on it should >be relatively uncontroversial. It seems they are not very much for having Django in adodbapi, and flangy says they've been developing towards an mssql-only setup. To me this is ok, it avoids certain kludginess. So we could have django-access for example if someone really wanted to use ms access with django, which would go through adodbapi. >This is all IMHO, of course. I don't know what the django-mssql guys >would think. But I think adodbapi should focus on being a dbapi >implementation, and let the various ORMs provide the adaptors, much >like how they handle sqlite or postgres or mysql. I tried to find an sqlite library for IronPython and could not. This project would really want to go forward and it pulls me with it, so I figured I'd test the code with sqlite. Could not. Would it have to go through adodbapi too? Now that I'm trying to find my focus, I think I'm going to proceed with Django 1.1 and django-mssql and trying to fix this import problem "ImportError: No module named sqlserver_ado.base" that I got somehow out in my "kludgemssql" driver but can't remember what I did for it ;P -- mjt _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
