[DB-SIG] db wrapper naming
wnvcole at peppermillcas.com
Mon Aug 30 22:47:51 CEST 2004
I second the motion. The computer business is too full of TLA's. (Three letter acronyms). Any TLA is bound to conflict with some other TLA. PyDBI is a name that even I would be able to remember.
From: db-sig-bounces at python.org [mailto:db-sig-bounces at python.org]On
Behalf Of M.-A. Lemburg
Sent: Monday, August 30, 2004 1:51 PM
To: Randall Smith
Cc: Python DB-SIG Mailing List
Subject: Re: [DB-SIG] db wrapper naming
Randall Smith wrote:
> Since our discussion here about a dbapi2 wrapper, Peter Hunt and I have
> been working on it. We have it mostly working with the ability to work
> with Python datetime and mx.DateTime types and changeable paramstyles.
> We have been discussing names and are leaning on dal, an acronym for
> Database Abstraction Layer. This package will have a subpackage named
> dbapi that will contain all of our current work. Future work outside of
> the dbapi wrapper scope will reside in other packages within dal.
> I'm posting here to get opinions/suggestions about these naming
> conventions so that we can identify any problems that may arise from it.
> We would appreciate your opinions and suggestions.
After all, what you're doing here is rather similar to what
the Perl folks did for their DBI interface.
Professional Python Services directly from the Source (#1, Aug 30 2004)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
DB-SIG maillist - DB-SIG at python.org
More information about the DB-SIG