How To Disable Caching Correctly In Sqlalchemy Orm Session?
Solution 1:
SQLAlchemy doesn't cache on itself. Unless you explicitly implemented a cache, like this one.
Pass echo=True
to your sessionmaker
and look into the logging
output.
Solution 2:
The problem in your code is due to database using REPEATABLE READ isolation level by default, so the query returns the same result unless you call commit()
or rollback()
(or use autocommit=True
as Xeross suggested) or manually change isolation level.
Yes, SQLAlchemy does cache mapped objects (not query results!), because ORM pattern requires single object for each identity. By default SQLAlchemy uses weak identity map as cache, so object is automatically expunged from session when there is no references left to it. Note, that subsequent queries will update state of cached objects with new data, so no need to worry about this cache.
Solution 3:
Hmm I already found the answer, you apparently need to explicitly do session.commit() to get it to update, or you need to set autocommit=True on the session, through for example the sessionmaker.
sessionmaker(bind=self.engine, autocommit=True)
However I haven't tested the session.commit() way
So this isn't a caching issue it seems to be just the way transactions work
Solution 4:
don't use autocommit=True and expire_on_commit=True
for state in self.identity_map.all_states():
state.expire(state.dict, self.identity_map._modified)
you can: after Query :db.session.commit()
Post a Comment for "How To Disable Caching Correctly In Sqlalchemy Orm Session?"