Russell Keith-Magee wrote: > On 5/2/07, mo <[EMAIL PROTECTED]> wrote: >> Hi, >> I'm new to Django... >> Is there any special reason that Django does not support DB2? > > The obvious reason is that nobody has offered to provide a backend > implementing DB2 support, and it hasn't been required by the core > developers. There may be technical reasons, but I don't know anything > about DB2 in practice.
Hello, I made a 'sort-of' DB2 backend for django [1]. 'sort-of' meaning that it's not near complete and only partially works. On a side note, making this I realized how 'bad' I was using django generally and how 'simple' things can be when django is used 'the right way' ;+). <details> I wanted to create a report out of a (legacy) DB2 on Z/OS mainframe, with very limited resources other than a linux box with a db2client and my beloved python, yet I couldn't 'update/insert/delete' in this database for obvious (important legacy :) reasons, so the 'save' and 'creation' parts of the backend aren't complete (yet they aren't difficult, I just left a 'pass' there to not make any "you're fired" mistakes). So I used the multi-db branch as my starting point with sqlite as the main database and only my application using db2. Since it didn't require anything else than adding the db2 directory with my code under 'backends/' I bet it also would work on trunk without any further modifications. One of the things that I needed and actually worked very well to my surprise was the introspection of the whole database I had to play with, very few fields were guessed and left as TextFields, and the models created worked perfectly (the database is nicely designed), only indexes were missing, but since I didn't need them (no creation) didn't tried further to complete that part. ForeingKeys, and even primary_keys with two columns were detected and worked just fine. Of the (few) problems I ran into, the main one was the (unmaintained?) PyDB2 module, which I discovered had some ugly memory leaks and bad (bah, I just didn't like it) parameter handling, where, again, I only fixed what was troubling me. The other 'issue' is that since I'm not a 'DBA' nor a DB2/SQL guru (in fact I learned every DB2 thing as I wrote this backend), and there are a few 'implementation' details that I'm not comfortable with, biggest example being namespaces/creator suffixes to tables for the introspection and models, were I just added a django.settings variable to specify which one I wanted, and it created the models with the suffixes already in the table names. Another example are the SYSIBM tables I used for the introspection part. I'm not quite sure they're all 'the same' among different DB2 versions (I'm accessing an 8.1 db2 database by the way). </details> > > If you want to contribute to Django by adding DB2 support, you would need to: > - Provide a set of patches implementing a DB2 backend Out of curiosity, what if no patches to trunk other than new code is needed? This was my main goal while making this backend, since I wouldn't want to fix again and again any django goodness every time I checkout svn, and besides the new 'setting' for the table suffixes nothing else is required afaics. > - Demonstrate a commitment to support the backend long term. We don't > want to add the DB2 backend, only to have it be orphaned (which, > unfortunately, is the current state of the ADO/MS SQL backend). > While looking for something already made, I saw a blog post [2] from a IBM DB2 developer talking about making a proper python-db2 module and a django backend not many months ago, but it looks like this guy liked more ruby than python ^_^. I've sent an email to him with my working yet incomplete backend to find out if there was any interest on this but no answer yet :+(. > If you want to see how to do this in practice - check out the > discussion around the Oracle support branch. Work on Oracle support > started in November, and is only now reaching the stage where it can > be merged into trunk. The Front Range Pythoneers (A python users > group) developed the patch, and is adopting the backend to provide > long term support. This group provides the perfect model for how new > DB backends should be supported. > > Yours, > Russ Magee %-) > [1]http://thepaya.homeip.net/svn/projects/django-db2/trunk/ [2]http://www.antoniocangiano.com/articles/2007/03/15/python-django-and-db2-we-need-your-input --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
