I think Aaron's simple object layer is trying to address this in
part, but it would be great if we didn't have to have two entirely
different object layers in SQLAlchemy. It seems more ideal to have
one basic layer that can behave either way, depending on your
applications' needs.
If the layers' behavior is so different, though, you're going to end up with a mess if you try to cram both into the same API.
--
Jonathan Ellis
http://spyced.blogspot.com
