Thanks Mike. Thought at least one person should give you the feedback you
asked for. I must confess I only read your source code and skipped the
documentation.
You may consider stucco_auth's demo application as a counterargument to the
pyramid_sqla design although you could use both packages together. There's a
very small chance that you might also be interested in z3c.saconfig, another
package that attempts to create a global registry of named SQLAlchemy
engines and sessions (and works with the ZopeTransactionExtension by
default).
I'm glad you have thought about `add_engine`. I still think it would be
better for the users to just teach them to type `sqlalchemy.create_engine()`
off the bat by reading the third paragraph of the SQLAlchemy ORM tutorial.
They are going to have to learn SQLAlchemy anyway, SQL eventually, and the
package happens to have an amazing manual that's worth reading all the way
through. The hard parts are things like many-to-many relationships with
foreign keys and circular dependencies in declaratively mapped classes, not
engine creation.
I actually do have to use two database engines that do not participate in
the same transaction (so I cannot use Session(binds={})). Instead, each
database has its own configured session factory. (Upper-case Session is the
session factory, lower-case session is an instance of the session, but with
scoped_session the session factory can be used in almost every case where
you would want an instance.)
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en.
