Issue 110349 - A workaround for the unreliable saving mechanism of OOo
Summary: A workaround for the unreliable saving mechanism of OOo
Status: CLOSED DUPLICATE of issue 102081
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 3.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-24 05:28 UTC by de_logics
Modified: 2017-05-20 10:01 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description de_logics 2010-03-24 05:28:24 UTC 
As discussed from issue 102081, the workaround for this problem is making a
single backup copy of the file before saving the changes. This can be preferably
done in the same location where the original file lies. After the save operation
has been successfully completed, this backup will be erased. If the system fails
during the save operation, and OOo realizes that the main file is corrupt, it
will give you an option to replace it with the backed up version of the file and
also rename the backup version so as to make it non-hidden or change it's
attributes in case if a windows system.

issue 102081 is a major flaw and should be fixed fastest possible IMO. It cause
me major loss of data.
Comment 1 Rainer Bielefeld 2010-03-24 06:41:11 UTC 
illegal clone of Issue 102081

@de_logics
If you have new arguments (for example why the auto backup mechanism can't be
satisfying) please discuss in original Issue 102081!
Comment 2 Olaf Felka 2010-03-24 08:12:06 UTC 
...
Comment 3 de_logics 2010-03-24 17:42:21 UTC 
The solution as discussed in Issue 102081 was a temporary workaround and I
actually did file issue 102605 where es suggested the problem of the large
amount of backups produced, which is right.

This flaw as in the saving mechanism of OOo can be best resolved this way, there
 is reality no other workaround to the problem as stated in issue Issue 102081;
rewriting the whole saving mechanism is not an option.
Comment 4 de_logics 2010-09-24 13:37:27 UTC 
Is something gonna happen to this or are people continue to loose their data?


This happened second time to me. Thanks to that backup (or the temporary
workaround), all effort was not lost.
Comment 5 de_logics 2010-09-24 16:41:47 UTC 
Ok, 2 more examples.... more effort lost. And the issue continues to be ignored.

Maybe I'll make a large announcement about this in other communities.
Comment 6 Rob Weir 2013-02-19 01:29:39 UTC 
Duplicate of 102081.  If we need to reopen 102081, then let's do it, but we shouldn't divide the discussion.

*** This issue has been marked as a duplicate of issue 102081 ***