Randall wrote:
> Thanks. I'm guessing your metadata is bound to an engine (mine uses
> dynamic binding).
Quite right. From the top of my model.py:
engine = __engine__ = PackageEngine("nossatv")
activemapper.metadata = BoundMetaData(engine)
I'm not at all sure this is the right way to do things -- I'm just
trying to get a prototype right now, and will worry about scalability
(and thread safety) later. It *does* have the advantage of working, and
I presume that there will be a Right Way documented after Kevin takes
his promised look into ActiveMapper integration.
> ActiveMapper is a class to facilitate declarative
> creation of tables, mappers, etc, but what is activemapper. Is that a
> module you imported from somewhere?
import sqlalchemy.ext.activemapper as activemapper
> I'm thinking I should be using sqlalchemy.objectstore, but I'm quite
> confused now and trying to sort things out. The new API encourages the
> use of sessions, but when using threadlocal,
>
> import sqlalchemy.mods.threadlocal
>
> Then objectstore is available and I'm not sure how to make the
> connection and use objectstore. With sessions I do
> create_engine(bind_to=engine). If I get through floundering, I'll post
> what I found out.
Let me know, too.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
