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

Tom Jenkins tjenkins@devis.com
20 Jun 2002 18:39:08 -0400


On Thu, 2002-06-20 at 17:20, Dustin Sallings wrote:
> Around 22:35 on Jun 20, 2002, M.-A. Lemburg said:
> #
> # 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.
> 
> 	Yes I have, and I've used a couple of different modules under it.
> I understand that it's progress from having nothing to conform to at all,
> but it's still ambiguous enough that people are writing wrappers to access
> databases generically.
> 

If it wasn't clear, I'm happy that there was progress to DBAPI 2.  I
picked up python as DBAPI 2 came out.  It is usable, especially if you
only work with one adapter.

paramstyle (forgot about this one) - this was another one that got us. 
letting driver developers pick from a set of paramstyles means a
hodge-podge of implemented paramstyles.  we generate alot of our sql, so
this becomes another extra step to make sure our generated paramstyle
matches the style for the adapter we're using.  is there a reason there
are 5 different styles?  can we narrow this down to maybe one? <wink>

i don't have any problem with driver developers adding extra custom
methods (ala pyscopg's dictfetchXXX).  if i use a custom method then i'm
taking responsibility.

-- 

Tom Jenkins
Development InfoStructure
http://www.devis.com