Re: [sqlalchemy] Selects after an update ?

Thanks Michael. I think this has everything to do with the fact that I'm running autocommit=True and the default expire_on_commit=True ! According to ticket 2041 , all my flushes reload objects ! Does this explain why, if I wrap the above code in my

Re: [sqlalchemy] Selects after an update ?

commit() expires all data by default so that current information is available in the subsequent transaction - while I don't see the mentioned begin/commit() block or specific SQL logs in the example you gave, it appears likely that some access of the Squares objects themselves would incur a relo

[sqlalchemy] Selects after an update ?

Trying to figure out why my logs are showing a group of SELECT statements after an update. I'm using Elixir on top of SQLA in the following fashion: squares = Squares.query.filter_by(user=user_record).all() for sq in squares: sq.sxsw_status = elixir.session.flush() return Nothing else uses th