Hi,

--- In firebird-python@yahoogroups.com, "Patrick Fitzgerald" > Hi
everyone - I'm not sure if this has been posted about before, but

> the python-based Django web framework is on its way to a version 1
> release.

Yup, finally there is a stable release with unicode support.

> This exceptional system is lacking full featured support for
> firebird/interbase. (ie there is version that does work, but
> development appears to have stalled)

Yes, because there is not a lot of interest from django staff for it.

> I was wondering if anyone with experience in both python and

firebird

> take a look at the backend code and have a stab at completing it?

I was trying to push Firebird support for django some time ago; ivan
picked it up and got it working. There are, however, some problems
that are not exactly thrilling to resolve for using FB with django
now:

1) Django developers are not interested into supporting another
backend. Thus, we were expelled to create external project. Not much
for a problem, except for...
2) As it is now, Firebird backend requires patching django. Most of
problems (like 32chars max length for constrains) are already solved
inside django, but using hacky if backend == "oracle" tricks.
3) Original patch was written for pre-1.0 django SVN and needs some
work for updating

Ivan's problem AFAIK also was that he's stuck with FB < 2.1. FB 2.1
features some nice things, so we're not required to hack around them
on django level, so perhaps there is a room for some simpler patch.

As for me, I'm not very excited about django test framework.
Showstopper for me is that I'd need to have patched django, which is
causing deployment problems, thus I swiched to another database.

However, I'm not using Django very much yet, so it's possible I'll
return to this project later and create something for FB 2.1+.
Meantime, I guess that there is a search for someone with spare
weekend or two ;)

Almad