To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=93071


User pancapangrawit changed the following:

                What    |Old value                 |New value
================================================================================
                Keywords|needmoreinfo              |
--------------------------------------------------------------------------------
                Priority|P3                        |P2
--------------------------------------------------------------------------------
                 Summary|Crash recovery: changes in|Autorecover: changes to au
                        | temporary recovery odb-fi|to-recovered file lost aft
                        |le lost after quitting    |er closing OOO
--------------------------------------------------------------------------------
                 Version|OOO300m3                  |OOo 3.0
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Sat Dec  6 14:32:08 +0000 
2008 -------
I am using PostgreSQL with JDBC now and OO3 release with leopard. The issue is 
still there. When this 
happens (which is admittedly very rare) it can destroy a lot of work 
unrecoverably. I repeat a somewhat 
rephased description of the issue, maybe I couldn't make myself understood well 
the last time:

- crash a database (well, we need a crash).
- restart and let autorecovery do its job. It should open the database you were 
working in for you (at 
least that is what appears to happen).
- create a new query and save it.
- close the database.
- reopen it: the query you created after the crash-recovery is gone.

This is, because crash-recovery does not open your original database for you, 
but a copy (called 
something like dbname_01.odb). After crash-recovery you work in that temporary 
file (without 
knowing it), all you modifications are saved to that file. When you close OO, 
this file is deleted and your 
work gone. The original file will open as if nothing had happened. One doesn't 
meet tis issue too often, 
because Base doesn't crash too often (for me), but if it happens it can be 
quite catastrophic...

I posted this issue to the dba-users-mailinglist and one other user reported 
that he had also met this 
issue on OSX. I do find this a serious problem, so I raise priority and 
reassign to dbaneedsconfirm. 
Hopefully somebody will react.



---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to