Hi,
Does this create new connection with the same name or start using the
> existing one? I'm almost 100% that latter, just making sure.
It should re-use existing ones, in a fairly intelligent way. Still, I'd
suggest doing some load testing before going live with this.
> Right now I'm binding meta to the engine, which obviosly makes all the
> tables work with the last engine plugged in
Ok, don't do that, not thread safe. You probably want all your tables in a
MetaData that is not bound to any database. Bind your sessions to the
user-specific engine. I'd suggest starting off with manual sessions. You
probably can do this using scoped_session, just get it working with manual
sessions first. One consideration is that this won't work if you have
multiple databases. At the moment, it's pretty much impossible to support
multiple dbs in this configuration.
> select([func.count("*")], from_obj=[sell_table]).sess.execute()
How about:
engine.execute(select([func.count("*")], from_obj=[sell_table]))
Paul
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
