FWIW, the separation of generating SQL and executing SQL was my intent in designing this: https://github.com/iffy/norm Currently, it *only* has asynchronous SQL execution, but it wouldn't be hard to add synchronous execution. Also, there's no subclassing of modeled classes. Matt Haggard On Wed, Aug 21, 2013 at 12:35 PM, Glyph <glyph@twistedmatrix.com> wrote:
On Aug 21, 2013, at 11:05 AM, Jonathan Vanasco <twisted-python@2xlp.com> wrote:
Having a great ORM for twisted is wonderful , but its way less exciting and attractive if it's only for twisted.
Doing this is simple, although probably not easy: you just need to convince the SQLAlchemy folks to separate the process of generating SQL and executing SQL, and expose hooks for event-driven frameworks (which is an ever-expanding circle now, encompassing Twisted, Tornado, Pulsar, and Tulip) to schedule SQL execution with an event-driven backend rather than assuming it can block.
When I faced this problem, I wanted to use SQLAlchemy rather than write my own ORM, but I was unable to due the lack of a public API for generating cross-database SQL.
-glyph
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python