On Jan 16, 2010, at 7:35 AM, Ergo wrote: > Yes, I understand that, but to my understanding if I have a setup of 4 > pasters, and i use expire_on_commit=True, if paster1 does a commit(), > while paster4 was in the middle of request somerhere, then it will > not be aware that commit was issued and will not re-fetch the data in > the middle.
paster4, if in the middle of a request, we also assume is in the middle of a transaction. If your database uses a high degree of isolation (typical, except for MyISAM), paster4 will not see paster1's new changes until it completes its transaction. SQLAlchemy has no capability to override this behavior since its your database. SQLAlchemy's "expire_on_commit" feature is part of its current strategy to place the job of concurrency on the side of the database, where it belongs. > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" 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/sqlalchemy?hl=en. > >
-- You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en.
