I am using SQLAlchemy for a multi-threaded daemon. MySQL is my backend. I use it in declarative mode with scoped_session and auto_commit set to False. Each thread requests for a scoped_session when it is spawned inside of the thread and then closes it when it is supposed to die.
I see in my mysql query logs that there is a commit and then it is immediately followed by a rollback. Is this normal? Will this affect my performance in the long run? I have been perf testing the daemon locally before pushing it to prod and wanted to get some pointers as to why this is happening. Thanks -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/t0Kwl0H9hGUJ. 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/sqlalchemy?hl=en.
