On Jan 16, 2010, at 8:30 AM, Ergo wrote: > 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 ? its a great idea to have it on. If you are commiting in the middle of a request, then doing further operations, you'd want the most recent info. Since by committing, you are saying to your environment, "heres the data, everyone else can now see it. now id like to see what you've all committed". Otherwise you shouldnt be committing until the request is complete (which is more typical). If you were comimtting only at the end, you see expire_on_commit would have no effect. You commit, close out the session, next request reloads the data anyway. > -- > 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.
