I am evaluating SQLAlchemy for a new project we are starting up and it looks great. The only remaining question I have about it is if there are some recommended best practices for using it as a agile-data style persistence layer for application development. (something like: http://www.ambysoft.com/essays/persistenceLayer.html)
The basic idea of a persistence layer (as I understand it) is that you attempt to isolate applications from the database to the point that the application and the data model can vary independently without requiring major code changes. As the paper above puts it, a well build persistence layer for an application should allow moving tables, renaming tables, renaming columns, and reorganizing tables without affecting the applications that access them. I am not optimistic enough to think that any system is *that* good, but it looks like someone could get quite a bit done towards that goal using SQLAlchemy if they worked at it. My current list of best practices to accomplish this goal includes: * explicitly set column names in the data mappers to avoid dependencies on column names * keep all mappers and setup in one common module that you use everywhere * use the sql construction language for all queries As you can see, my list is quite short. :) Does anyone have additional suggestions for someone just getting started with SQLAlchemy? Thanks, Allen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
