[DB-SIG] Experiences with DB-API2.0

[M.-A. Lemburg]

> Around 18:11 on Jun 20, 2002, Juli?n Mu?oz said:
> 
> # It seems that a multilayer architecture like the one you have done is a
> # good solution (and I think the more natural), for the driver developpers
> # and for the end users (developpers who write applications), and if some
> # day it is released, and documented, it will be very nice.
> 
> 	I would argue that creating a less ambiguous DB API would prevent
> people from having to create such abstractions in the first place.  I
> don't really understand the point of a DB API that requires another layer
> of abstraction before a programmer can begin to use it.  The abstract
> interface maintainer must be aware of every driver that gets written and
> write custom code to deal with it, and then where are you?

Just curious: have you ever used one of the DB API module
yourself ?

It is because of the DB API standard we have in Python that
there are so mance different database interfaces around.

-- 
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
______________________________________________________________________
Company & Consulting:                           http://www.egenix.com/
Python Software:                   http://www.egenix.com/files/python/
Meet us at EuroPython 2002:                 http://www.europython.org/