Chris Withers wrote:
> M.-A. Lemburg wrote:
>> If you want yet another abstraction layer between your code
>> and the database, that's the way to go, yes :-)
>> SA does provides a general abstraction layer, not the application
>> specific one I was talking about.
> To be honest, I'd prefer to use a powerful, lean, well tested
> abstraction layer that's tested by a lot more people than just me rather
> than hacking up a specific abstraction layer on each and every project ;-)

That's not what I'm talking about. Each application has its own
database requirements and it's common practice to centralize this
functionality into an application specific database abstraction layer.

You can, of course, have this layer use SA to add another layer
of abstraction between the application database layer and the database,
if you feel uncomfortable with SQL, or want to abstract the queries
from their database specific SQL implementation, e.g. in order to
support more than one database backend.

Marc-Andre Lemburg

Professional Python Services directly from the Source  (#1, Aug 27 2010)
>>> Python/Zope Consulting and Support ...
>>> mxODBC.Zope.Database.Adapter ...   
>>> mxODBC, mxDateTime, mxTextTools ...
2010-08-19: Released mxODBC 3.1.0    
2010-09-15: DZUG Tagung, Dresden, Germany                  18 days to go

::: Try our new mxODBC.Connect Python Database Interface for free ! :::: Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
Zope-DB mailing list

Reply via email to