From: Henrik Eriksson <henke.eriksson@gm...> - 2007-02-22 09:22:00
(Note: when I refer to jython below I mean a future 2.3/2.4 release).
I sent a mail to Frank the other day asking him about his experiences
with using SQLObject with jython (he mentioned trying it on the list a
couple of months ago) and he thought I should take the discussion to
Getting SQLObject or SQLAlchemy running on jython is one step in the
right direction towards turbogears support.
Right now SQLObject is the main ORM for turbogears, but in the future
it looks as though SQLAlchemy will take that place.
After looking a little closer at the code in the two projects I am
tempted to jump right into implementing support for SQLAlchemy since
it has a cleaner internal design separating dbapi implementations from
SQL dialects a bit better than SQLObject.
Does anyone have any experience with trying to get jython working with
these frameworks? Any opinion on which one I should focus on?
What needs to be done (at the very least) is to add support for zxJDBC
as a connection (SQLObject) or engine (SQLAlchemy). This
implementation in turn needs to be able to supply "dialect"
information for a number of supported databases and my hope here is to
use the dialect-parts of the existing code in the projects.
Well, that was a very short intro... hopefully we can get a discussion
going here... although the main goal should probably be to add zxJDBC
support to the chosen framework, not in jython itself.
I have only "looked at" code so far, but hopefully I will get the time
to run some tests within a few days.