i'm using sqlalchemy in pyramid, under uwsgi. i've been reading up on forking issues that can arise in this stack.
from what I understand, issues arise because the "SqlAlchemy Connection" is established before the fork, resulting in each forked process potentially trying to use the same connection. One of the fixes is to (re)connect after the fork. This is where i'm confused... I don't know what a "SqlAlchemy Connection" refers to. I've read up on the uwsgi, sqlalchmy and pylons lists + docs -- I can't get any better info on what this SqlAlchemy connection is, or what component is having the issues. If the issue is with the SqlAlchemy engine connecting to the database, and it's internal db connection, then I should be fine -- SqlAlchemy doesn't connect in my apps until the first request. I verified this with postgresql logs. If the issue is with creating a SqlAlchemy engine or sessionmaker, then I will need to rewrite some stuff. Does anyone know the specifics of the "connection" that has fork issues? -- 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.
