Hi David,
Currently, i'm not doing anything too terribly complicated with
sqlalchemy. the real app i'm working on is doing something slightly
more complicated, but as an example...
code
from sqlalchemy import Table, Integer, String, Column, Boolean
from petetest.rdb import engine
#engine is just
Hi Pete. Thank you for your reply. I have been interested in a similar
integration of SQLAlchemy with Zope as SQLObject and it was evident
other folks are already using it in Z3. I was curious how people have
been dealing with transactions with some hope that something could be
formalized with
David,
I'm excited to see the amount of discussion over sqlalchemy's
integration into zope. nothing against sqlobject, but i really enjoy
sqlalchemy, and i'm glad to see it getting so much attention...
looking over what Jurgen has sent across, the tying of sqlalchemy
directly into the
Hi Pete. I think the timing is good since SQLObject is likely to undergo
some changes. Ian has setup a SQLObject2 and an DBAPI type package
recently to move it forward in a way unencumbered by his original
project. That said, choice is a good thing and choosing an ORM to best
accomodate a
I agree with Marco that the use case i can most readily imagine for
needing to tie zodb objects back to an rdb is to allow people to run
reports or get at historical data in more conventional ways...
I've had to make allowances for that in a number of projects i'm
currently working on for
Hi Pete. I have been looking at SQLAlchemy for Zope3. Can you advise how
you are using this with zope's transactions. It seems that there are
some folks using SQLAlchemy with Zope3 for sure. I am hoping to see a
few things formalized somewhere or some work on assembling a small
package like
