Hi Nathan/Russell

I believe Nathan has already included IBM_DB2 also as a part of
documentation. Thanks Nathan for that. Coincidence that DB2 support
and SQL Anywhere support for Django came about the same time.

Thanks and Regards
Tarun Pasrija
Open Source Development
IBM India Software Labs

On Jun 24, 7:27 pm, Russell Keith-Magee <[email protected]>
wrote:
> On Tue, Jun 23, 2009 at 10:37 PM, Nathan Auch [Sybase]<[email protected]> 
> wrote:
>
> >> Open a ticket requesting this so the idea isn't forgotten. If you can
> >> work up a patch that contains some draft text, feel free to push the
> >> ticket onto the v1.1 milestone.
>
> >> If you're going to write some draft text, keep the following in mind:
> >>  - Sybase isn't the only external backend, so the text you provide
> >> will need to be easily expanded to include links for DB2, MSSQL, and
> >> any other backends that come along.
> >>  - The text needs to be clear that the backends are unofficial, and
> >> supported by the end-project, not by the Django project itself.
> >>  - I can think of at least two places that will need to be patched:
> >>     * docs/topics/install.txt
> >>     * docs/ref/databases.txt
> >>   Of course, if you find anywhere else where a note would be
> >> appropriate, feel free to make a suggestion.
>
> >> Thanks again for taking the time and effort to support Django!
>
> > I've filed ticket #11356 to track this issue and included a patch to the
> > documentation.
>
> ... and committed in [11093] and [11098]. Thanks Nathan. I hope the
> shiny new link gives you a flood of new users :-)
>
> Yours,
> Russ Magee %-)

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to