Long transaction in web application
Does anyone have any suggestions on how to implement the following?
In my web application, all changes to the data should be done inside an "edit session". Only one user may have an edit session at any given time, and the changes should be invisible to the other users until the edit session is ended and the user choose to "commit". The user should also be able to end the edit session by discarding all changes ("rollback")
Basically ACID-requirements..
A database transaction seems like a perfect fit, if it wasn't for one thing: the edit session spans multiple HTTP-requests (of course) and also multiple login/logouts. The duration in time could be hours, or even days.
I'm using MySQL 5.0 and Ruby on Rails.. Thanks in advance.
Subject
Views
Written By
Posted
Long transaction in web application
2919
April 23, 2008 02:40AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.