[DB-SIG] db wrapper naming

[M.-A. Lemburg]

Ian Bicking wrote:
> M.-A. Lemburg wrote:
> 
>> 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.
>>
>>
>>
>> PyDBI ?
>>
>> After all, what you're doing here is rather similar to what
>> the Perl folks did for their DBI interface.
> 
> 
> Why the "Py"?  Isn't it kind of implied?  I like dbi, though.  Maybe the 
> project name would be PyDBI, with the module name being dbi?

The name "dbi" is already taken (by DB API 1.0 which required
such a module, see e.g. the win32 odbc module).

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Aug 31 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 ! ::::