Issue 93737 - changes made to a "Save-As"ed database document are stored in the original document, corrupting it this way
Summary: changes made to a "Save-As"ed database document are stored in the original do...
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO300m5
Hardware: Unknown All
: P2 Trivial (vote)
Target Milestone: OOo 3.0
Assignee: marc.neumann
QA Contact: issues@dba
Keywords: regression
Depends on:
Blocks: 88888
  Show dependency tree
Reported: 2008-09-10 21:13 UTC by Frank Schönheit
Modified: 2009-07-20 15:59 UTC (History)
1 user (show)

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

document to reproduce the bug case (1.96 KB, application/vnd.sun.xml.base)
2008-09-10 21:13 UTC, Frank Schönheit
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2008-09-10 21:13:02 UTC
- open the attached database document
- File / Save as ...
- save the document under an arbitrary name/location other than the original
  one; let's name it "copy" for more clarity in the below items
- select the "Tables" section at the left-hand-side
- delete the table "abc" from the document
- close the document
- exit
- start, again
- open the original document
- select the "Tables" section at the left-hand-side
=> the table "abc" does not exist anymore
- open the database document to which you saved the original document ("copy")
- select the "Tables" section at the left-hand-side
=> the table "abc" is still present

Effectively, this means that the changes you did to "copy" were not saved in
"copy", but in the original document - causing heavy data loss this way.
Comment 1 Frank Schönheit 2008-09-10 21:13:28 UTC
Created attachment 56400 [details]
document to reproduce the bug case
Comment 2 Frank Schönheit 2008-09-11 09:48:30 UTC
fixed in CWS dba30z
Comment 3 Frank Schönheit 2008-09-11 09:50:25 UTC
for the record: This was a very subtle side effect of the Title feature (the
application controller cached the URL of its associated document, and this cache
was formerly implicitly updated after a SaveAs operation, during determining the
new title. With the changes brought by the Title feature, this update did not
happen anymore, so the application controller used the *old* document URL to
obtain a connection. Thus, all changes made to the connection affected the old
document, not the new one).
Comment 4 Frank Schönheit 2008-09-11 12:31:13 UTC
fs-> msc: please verify in CWS dba30z
Comment 5 marc.neumann 2008-09-12 08:28:26 UTC
verified in CWS dba30z

find more information about this CWS, like when it is available in the master
builds, in EIS, the Environment Information System:
Comment 6 Frank Schönheit 2008-09-12 20:39:53 UTC
for the record: added test case
complex.dbaccess.ApplicationController.checkSaveAs for this scenario.
Comment 7 thorsten.ziehm 2009-07-20 15:59:00 UTC
This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
If you want to know more about the handling of fixed/verified issues =>