On 9 Jan 2006, at 21:21, Ammar Hakim wrote:
Sometimes, in the last step the browser still gets the
old data before the change was made. On a refresh,
however, the correct data is obtained. Further, this
problem does not always crop up: it seems that it
occurs if the particual DB operation is very fast. Has
anyone experinced a similar problem? Is there some
better way to ensure that the commit really happens
before the next query?

This is guaranteed to be a browser caching issue and has nothing to do with ZODB... IE is especially unreasonable when it comes to over- caching pages.


For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -  ZODB-Dev@zope.org

Reply via email to