> A quick question: do you have any idea of how much work it would take to port SQLAlchemy to Django properly? There is a version of this I have in mind that w

> A quick question: do you have any idea of how much work it would take to port SQLAlchemy to Django properly? There is a version of this I have in mind that would take at least 6-8 weeks of pretty solid developer time. A new layer would be built on top of SQLAlchemy ORM that would look just like Django mappings/QuerySet. The mappings wouldn't be too difficult, QuerySet maybe a little more. The advantage to that approach would be that existing Django mappings and QuerySet code could be reused in the context of a SQLAlchemy session conversation, that is, the unit of work/identity map paradigms would be brought in. A lot of the "bolted-on/doesnt-really-work" code I see to approximate these features in a tool like JohnnyCache wouldn't be needed anymore. I'm not sure that this really encompasses "manage" though, I'd have to increase my familiarity with that tool to know everything it does.