In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

View Revisions: Issue #682		[ All Revisions ] [ Back to Issue ]
Summary	0000682: Refactor "Item Open for Editing" mechanisms

Revision	2010-04-08 22:53:52 by Dmitry
Additional Information	We have data loss prevention system, that consists of several parts (all only in administrative console): 1. [on by default] Data from tables being edited not directly, but via temporary tables created for each user individually (when user clicks "Add"/"Edit" buttons). When user clicks "Save" button on editing form, then data is copied back from temporary table to original live table. 2. [off by default] When user clicks "Edit", then we are checking, that given record(-s) is not being edited by another user already and we are showing warning message to the user about that, so he can immediately cancel editing to prevent possible data loss 3. [on by default] when user clicks "Save" button on editing form we are locking table, so nobody else in that moment couldn't overwrite data user is saving right now Original idea by Sergey.

Revision	2010-04-08 22:52:38 by Dmitry
Additional Information	We have data loss prevention system, that consists of several parts (all only in administrative console): 1. [on by default] Data from tables being edited not directly, but via temporary tables created for each user individually (when user clicks "Add"/"Edit" buttons). When user clicks "Save" button on editing form, then data is copied back from temporary table to original live table. 2. [off by default] When user clicks "Edit", then we are checking, that given record(-s) is not being edited by another user already and we are showing warning message to the user about that, so he can immediately cancel editing to prevent possible data loss 3. [on by default] when user clicks "Save" button on editing form we are locking table, so nobody else in that moment couldn't overwrite data user is saving right now Currently it Original idea by Sergey.

Web Development by Intechnic

In-Portal Open Source CMS