Hello All,

I am using ZODB as a database for a web-application. I
am having some trouble with the commits, though.
Basically it seems that sometimes transaction.commit()
returns without the commit actually happening. Here is
the compelete senario:

1) user requests some changes to DB via the webrowser
2) application does the changes on server and does
transaction.commit()
3) DB is read again and HTML reflecting changes is
returned

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? 

Any help will be appreciated!

Cheers,
Ammar



                
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 

_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev

Reply via email to