On May 18, 2014, at 12:10 PM, Richard Gerd Kuesters <[email protected]> wrote:
> well, this part is still working, as long as i remember. my biggest problem > now - and has been for the last couple of years - is to manage this mayhem of > classes and engines AND sessions, because everyone "wants to go online" with > their data. i'm writting and rewriting a session manager that can simplify my > life for a looooong time, i got close to get things done with your > RoutingSession vertical example, but it doesn't work very well with > functions, session.query(...).count() or .exists() and so on. i'm writing > code as hell and still far from an acceptable, performatic session "router" > (?) for a class that can come from anywhere, for one or more specific > engines, without grind string ids everywhere. > > well, i think my problem have a lot of weaknesses to discuss ... but, one at > a time. > > for now, any tips on enterprise multi-everything session routing? :) > > you're trying to route to different sessions based on the intricacies of what's inside a SELECT statement? See I just would never do that, it's very complicated and error prone. I'd have an explicit node name sent in right at the top. Explicit is better than implicit. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
