Issue 54609 - Serious data loss in base tables when openoffice crashes
Summary: Serious data loss in base tables when openoffice crashes
Status: CLOSED DUPLICATE of issue 55493
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 680m122
Hardware: All Windows 2000
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-14 16:18 UTC by helgekraak
Modified: 2013-08-07 15:45 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description helgekraak 2005-09-14 16:18:46 UTC
Please do the following:

- Open Base Document
- open any table
- insert some text in a column
- close the table, confirm saving of changes in tables
- you will notice that the saving button in the main base GUI is grey (not so
important but should perhaps be mentioned)
- now kill soffice.bin in the windows task manager
- reopen the base file -> the recover dialog will appear (it only appears when I
kill the correct running soffice.bin like in my example here. It will not appear
if it crashed before and I killed soffice.bin after it already hanged)
- Neither when you do the recovery nor you don't do -> the before entered data
is gone! Even the data changes of several hours are completely gone if you
didn't close the program in between.

I tried the SHUTDOWN command before I killed soffice.bin. It doesn't make any
difference!

Regarding the HSQLDB documentation I thought that HSQLDB has a live tracking of
all changes in the database which offers the possibilty to recover changes later
 if there is a power off or a crash or something else similar. Am I wrong or is
it just not implented in base?

Best regards
Helge
Comment 1 marc.neumann 2005-09-21 15:44:11 UTC
HI,

I can reproduce the data lost, but I don't know if we can fix this. 

I reassign it to the right developer.

Bye Marc

Comment 2 helgekraak 2005-09-28 10:27:37 UTC
Ocke, just wanted to ask whether you have any idea, when you approximetaly could
perhaps fix this issue? I think for many of us this issue is a serious problem
because it makes a production use nearly impossible. I cannot tell users to
close and open the whole program every minute. For the moment I could also very
well live with some workaround that saves the database e.g. every minute. Do you
think that's perhaps possible?
A discussion about this was here:
http://www.oooforum.org/forum/viewtopic.phtml?t=24043 

Best regards
Helge
Comment 3 ocke.janssen 2005-10-04 07:27:56 UTC
Hi Frank,

please take care for this one. Thanks.


Ocke
Comment 4 Frank Schönheit 2005-10-05 12:29:20 UTC
This particular issue here is fixed now as issue 55493, with a tagret milestone
OOo 2.0.1 (sorry, I know that many of you will recognize this as "too late").

I resolve this one here as duplicate of issue 55493 (though this one here is
older, the other contains a more comprehensive description. Sorry, noticed this
too late when submitting the new one).

*** This issue has been marked as a duplicate of 55493 ***
Comment 5 Frank Schönheit 2005-10-05 12:33:34 UTC
closing duplicate