MS Access backend for django

views:

183

answers:

+1 Q:

MS Access backend for django

Hi django users--

I've been working on a modification of the django-pyodbc package so that it could be used with MS Access.

I need this for a legacy database we are tied to at my organization, and have been doing a rather hacky job specific to my situation, but have also been making useful, generalizable progress in terms of adapting SQL syntax for MS Access.

My question is, is this a project that anyone else in the world is interested in? should I clean up my code and try to fully generalize it, or is everyone else in the world able to solve their MS Access problems by moving to SQL server?

I would move the data to SQL Server if that is an option.

If moving the data is not an option and if my Django app is already connecting to SQL Server, I might just create a linked server on SQL Server and go through SQL Server instead.

celopes 2010-02-05 00:28:33

I mostly finished the implementation (introspection + admin system = working, test suite = unfinished), but I have two issues, limitations of the JET ODBC engine:1. 127 column limit in a SELECT query in Jet 2. Performance = awful.From the link above:"Usage of such data are only limited by the limitations of the Access database. In MS SQL 2005 server the external data is accessed through the OLEDB interface, and the limitations are those imposed by this provider."Does anyone have info that might shed light on whether linking servers would provide a workaround for speed or column limit?

James 2010-02-12 00:08:00

+1 A:

I actually do have a need for this utility, care to share your code?

bwooceli 2010-03-12 20:58:10

absolutely. the django-pyodbc guys are interested in the code as well, so I'm going to clean it up and make it compatible with (as much as possible of) the test suite. I'll let you know as soon as I get it ready for somebody else's consumption.

James 2010-03-16 19:51:13

ansaurus

tags:

views:

answers:

MS Access backend for django

related questions