We are still interested in providing the adaptor. Look forward to the
'Getting Started'.
Regarding the 'Maintaining problem', this is not a problem as
evidenced by the IBM Rails adaptor project as Rails has progressed
from 1.x to 2.x
On Apr 14, 2:26 pm, Robert <[EMAIL PROTECTED]> wrote:
> If have
If have I understood problem well:
- ibm guys are developers
- community guys are supporters
- developers may NOT look existing code
- developers may look at technical specification
- since django hasn't got specification for writing backend -
developers can't do anything
- supporters may l
Since I'm the originator of this thread, (thank me or curse me), I'll
be glad to help out in whatever ways possible. I know Jacob said he
was going to write the documentation for this. What kind of
assistance can I provide?
I'll be glad to test the driver that eventually gets written as well.
E
On Tue, Mar 25, 2008 at 4:59 AM, Ned Batchelder <[EMAIL PROTECTED]> wrote:
> Unfortunately, django.db.backends.dummy falls below the bar for minimal API
> documentation. While it may have the names of the entry points, they are
> all defined as complain(*args, **kwargs), and they have no docstri
Posting my humble $.02 on this interesting subject:
Given the existance of a django.db.backends.dummy module that probably
contains, in *some* form, all of the required information to produce a
document with "API signatures and entry/exit conditions", i would say
the easiest to go is to hire (or
I thought I would end this standoff by simply going where James pointed,
and turning it into the minimal "spec" Alex describes. I know next to
nothing about db backends, but it sounded like this was a job for a
scribe, not a developer.
Unfortunately, django.db.backends.dummy falls below the ba
On Mon, Mar 24, 2008 at 11:15 PM, Alex P <[EMAIL PROTECTED]> wrote:
> 1. The original message was in brief: there is a growing interest in
> the Python community for DB2 support, and we (developers behind IBM_DB
> driver, DB-API wrapper and SQLAlchemy adapter) are interested to help
> in the D
Not because I'm never going to give up, but because there are 2 points
that needed to be addressed, I am now resurrecting this thread once
more:
1. First, surprisingly but consistently, the message gets
distorted, and for the benefit of the original poster and at least 5
or 6 other Python and
Alex, Antonio, & Leon:
IBM should understand our frustration when a spec exists (in
`django.db.backends`) but, because it is in source code form, your
particular IBM department cannot look at it. Thus, IBM is attempting
to shift the burden onto our community to produce onerous technical
document
This is quite the discussion thread. I was having a hard time trying
to figure out where to insert the post.
Let me introduce myself. I am Leon Katsnelson and I am responsible for
Product Management for the IBM Data Management portfolio which
includes DB2 and IDS database servers as well as Data
10 matches
Mail list logo
