[sqlalchemy] Re: Persistence Layer best practices with SQLAlchemy

2007-01-27 Thread Allen Bierbaum
On 1/26/07, Michael Bayer [EMAIL PROTECTED] wrote: On Jan 25, 7:28 pm, Allen [EMAIL PROTECTED] wrote: 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

[sqlalchemy] Re: Persistence Layer best practices with SQLAlchemy

2007-01-27 Thread Karl Guertin
On 1/27/07, Allen Bierbaum [EMAIL PROTECTED] wrote: I agree that a complete separation is probably either a) impossible or b) going to lead to code that is so complex and difficult to maintain that it removes any advantage gained. I modify the schema and code in step during development, once

[sqlalchemy] Re: Persistence Layer best practices with SQLAlchemy

2007-01-27 Thread Michael Bayer
On Jan 27, 2007, at 11:57 AM, Allen Bierbaum wrote: As a side note, I am trying to see where ActiveMapper would fit into all of this. At first I thought that ActiveMapper would actually tie the classes closer to the data model, but after looking at it further I am starting to think that it

[sqlalchemy] Re: Persistence Layer best practices with SQLAlchemy

2007-01-26 Thread sdobrev
Mike, On a side note, do u have any ideas about supporting stored procedures in some way? Be it just knowing about them and maybe calling them, or on the other end, generating them? IMO they are _some_ way to hide some of those session.queries... Although i'm just extrapolating my own vision