| Subject | Re: django 1.0 and firebird |
|---|---|
| Author | almadrpg |
| Post date | 2009-03-23T19:56:16Z |
--- In firebird-python@yahoogroups.com, marius adrian popa <mapopa@...> wrote:
yup, I've contributed to the original patch. Problems with integrating django with firebird was:
1. queryset refactor branch, merged into django in django-pre1.0 that broke our patch completely
2. firebird backend cannot be integrated into django without patching it (because of some if backend == 'oracle' functionality that backend == 'firebird' needs too)
3. no chance for firebird to be merged into trunk (see http://code.djangoproject.com/ticket/1261)
However, Ivan worked much on (1), so porting should not be a big problem, I don't know what state of (2) is and (3) do not matter, kind of.
My interest shifted as I changed my job and am now restricted to MySQL thing...however, there should be a reasonable way to make FB work in not much time, as there are hg/git mirror to handle django fork and ORM is now in much better shape then two years ago.
FB 2.1 now also simplify things a lot and remove some hacks needed (especially around text blobs).
I'm heading to PyCon, so perhaps I'll have a time to look at it...if You'll have some progress meantime, please tell us ;)
(Honestly, my biggest problem is Django test suite, based on model doctest. It makes creating new backend not much fun, especially when there is no SkipTest for this_backend_do_not_support_this_and_we_know_it_please)
Almad
>Hi,
> anyone worked on django 1.0 or 1.1 and firebird ?
> I see some old patches and firebird backend in the svn
> http://code.google.com/p/django-firebird/
>
yup, I've contributed to the original patch. Problems with integrating django with firebird was:
1. queryset refactor branch, merged into django in django-pre1.0 that broke our patch completely
2. firebird backend cannot be integrated into django without patching it (because of some if backend == 'oracle' functionality that backend == 'firebird' needs too)
3. no chance for firebird to be merged into trunk (see http://code.djangoproject.com/ticket/1261)
However, Ivan worked much on (1), so porting should not be a big problem, I don't know what state of (2) is and (3) do not matter, kind of.
My interest shifted as I changed my job and am now restricted to MySQL thing...however, there should be a reasonable way to make FB work in not much time, as there are hg/git mirror to handle django fork and ORM is now in much better shape then two years ago.
FB 2.1 now also simplify things a lot and remove some hacks needed (especially around text blobs).
I'm heading to PyCon, so perhaps I'll have a time to look at it...if You'll have some progress meantime, please tell us ;)
(Honestly, my biggest problem is Django test suite, based on model doctest. It makes creating new backend not much fun, especially when there is no SkipTest for this_backend_do_not_support_this_and_we_know_it_please)
Almad