[sqlalchemy] Re: expire_on_commit=False running many load balanced instances of app

2010-01-16 Thread Ergo
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. -- You

[sqlalchemy] Re: expire_on_commit=False running many load balanced instances of app

2010-01-16 Thread Ergo
Basicly, im wondering if i have 4 separate app instances, im just not wasting resources to refetch the data here. In a multi server setup this doesnt seem to be a good idea to have this on ? Its transaction separation that should decide of this ? -- You received this message because you are

Re: [sqlalchemy] Re: expire_on_commit=False running many load balanced instances of app

2010-01-16 Thread Michael Bayer
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