[PYTHON DB-SIG] The Java API by comparison
Fri, 20 Sep 1996 16:06:04 -0700
>From: Michael McLay[SMTP:mclay@fermi]
>Sent: Friday, September 20, 1996 4:50 AM
>Subject: [PYTHON DB-SIG] The Java API by comparison
>I just ran across the Java DB interface definition and thought it
>might make a good starting point for reactivating this list. By
>comparison the Python DB interface is much smaller. Is this a feature
>of the language, or is the job of defining a Python DB API just not
>This brings me to the question of how we can start quantifying the
>quality of interfaces in Python. It would be very helpful to new
>users to have a rating system in place that indicates the level of
>completeness, performance, ease of use, and other parameters for a
>given interface. Without such a system the Python extension library
>will remain a black box in which lots of good stuff is mixed in with
>half baked and obsolete technologies.
Interesting thought. The DB interface, at least, has shown to be
complete within the bounds of the problems that I've used it for. Also,
that it has been more than workable for Oracle, Informix, and ODBC. It
was relatively doable for mSQL and PG95, but those two databases lack
some key features that I was looking for :-( and so I never bothered to
complete implementations along the DatabaseAPI line...
btw, Jim has grumbled for a while about some modifications to the API
and/or backing that up with some code. From some brief talks with him at
the Python workshop, they sound doable and are nice improvements, but
the ship is still out...
p.s. and yes... I promise to try to reorg the db-sig main page a bit and
the DatabaseAPI some to bring them up to date and have a visible link to
the api... this weekend.
Greg Stein, Microsoft Corporation execfile("disclaimer.py")
DB-SIG - SIG on Tabular Databases in Python
send messages to: firstname.lastname@example.org
administrivia to: email@example.com