On 5/2/07, Javier Villavicencio <[EMAIL PROTECTED]> wrote: > > 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' ;+).
Spelunking the internals is always a great learning experience :-) Even if your backend isn't complete, it might be a good starting point for someone else. If you feel comfortable sharing it, open a ticket requesting DB2 support and attach your patch. Make sure the comments highlight that it's incomplete/experimental. This might be all the impetus that is required to get the project rolling. > > 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. I'd be very surprised if any patches _were_ required outside the backend. The Oracle backend is a bit of a special case; we're taking the opportunity to identify some other pieces that need to be refactored. However, there is very little DB specific code outside the backends. However, the fact that the patch is limited in scope doesn't mean it will be immediately accepted into the trunk. We took this approach with the ADO/MSSQL backend, and we have ended up with a real blight on the Django source tree. The MSSQL backend is almost unusable because nobody is maintaining it. However, the backend is there, so people download Django, try to use MS SQL, and discover that that backend doesn't work. This leaves these some users with the impression that Django is of poor quality, when in reality, it's just the MSSQL backend - and it's one of the very few areas in Django where quality control is lacking. This situation is lamentable, but easily preventable - hence the 'no new backend unless it is supported long term' policy. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
