[DB-SIG] ANN: mxODBC Version 0.3

[M.-A. Lemburg]

Greg Stein (Exchange) wrote:
> 
> Bill makes some good points, but the one single thing that caught my eye
> last week when you first announced this was your tossing of the DBI
> module. I'd like to reiterate that that was really not a very good idea
> (IMO).
> 
> Exceptions are handled by identity. The single dbi module provides the
> exception that all db modules will raise. Clients can then catch
> "dbi.integrityError" and catch an error regardless of what underlying db
> module was used. The dbi module also provides a common set of type
> information.

Ok, I'll try to add a Python module named dbi that interfaces to
the values defined in mxODBC in just that way, if that's what
you are missing [...provided I find time to do so].

I've put that question up before: is there the one and only
dbi module that everybody should use, or is this just a
naming + content convention that everybody agreed on ?

Side note: For ODBC the type information given by the dbi
module is not needed.

-- 
Marc-Andre Lemburg


_______________
DB-SIG  - SIG on Tabular Databases in Python

send messages to: db-sig@python.org
administrivia to: db-sig-request@python.org
_______________