Bug 107653 - LO saves changes after you decline to save upon exiting Relation Design window
Summary: LO saves changes after you decline to save upon exiting Relation Design window
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
(earliest affected)
Hardware: All All
: medium major
Assignee: Not Assigned
Depends on:
Blocks: Database-Tables
  Show dependency treegraph
Reported: 2017-05-05 23:46 UTC by Terrence Enger
Modified: 2023-11-12 03:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

example database, embedded Firebird (2.99 KB, application/vnd.oasis.opendocument.database)
2017-05-05 23:46 UTC, Terrence Enger

Note You need to log in before you can comment on or make changes to this bug.
Description Terrence Enger 2017-05-05 23:46:41 UTC
Created attachment 133099 [details]
example database, embedded Firebird


(1) Download and open attached embedded_fb.odb.

(2) Take menu options Tools > "Relationships...".  The program
    presents window "Relation Design" with tables Table1 and Table2;
    note that there is no relationship defined between the two tables.

(3) Drag Table1.f2 and drop it on Table2.f2.  The program draws a line
    between Table1 and Table2.

(4) Take menu options File > Close.  Program prompts "Do you want to
    save the changes?  The relation design has been changed."

(5) Click <No>.  Program closes "Relation Design" window and returns
    focus to the main database window.

(6) Take menu options Tools > "Relationships...".  The program
    presents window "Relation Design" with tables Table1 and Table2.

    Observed : There is a line joining Table1 and Table2.

    Expected : No line.

These observations are from daily Linux dbgutil bibisect repository
version 2017-05-05 running on debian-stretch.
Comment 1 Buovjaga 2017-05-07 12:26:32 UTC

Let's raise severity as this can cause data loss.

Arch Linux 64-bit, KDE Plasma 5
Build ID: 6e4cba99bb35e6697b94309eedd1a08ebea2dc68
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on May 5th 2016
Comment 2 Robert Großkopf 2017-05-08 10:14:23 UTC
Couldn't confirm this behavior with OpenSUSE 42.1 64bit rpm Linux.
Works as expected with internal HSQLDB. (Added tables, closed relationship-window without saving, tables doesn't appear when reopening)

Unable to add any table when trying to create relations with internal Firebird (LO hangs when trying to add ...).

Creating the relationship doesn't work with Firebird: See bug 101230.

Tested here with version:
Build ID: 8da106529e85981ce37fbbd18160023c26cc7129
CPU threads: 4; OS: Linux 4.1; UI render: default; VCL: kde4; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-05-07_23:02:43
Locale: de-DE (de_DE.UTF-8); Calc: group

Same behavior with version:
Comment 3 Robert Großkopf 2017-05-08 10:18:47 UTC
Now I have opened the attached database. When trying to create a relationship between the tables an error appears: The relationship already exists. Seems to be the same reason as bug 101230 - window for relationships doesn't show relations of Firebird in the right way.
Comment 4 QA Administrators 2018-05-09 02:34:30 UTC Comment hidden (obsolete)
Comment 5 Terrence Enger 2018-05-10 00:11:54 UTC
I still see the problem in daily Linux dbgutil bibisect repository
version 2018-05-07.

Upon further consideration, my original expectation that declining to
save changes in step (5) still seems reasonable.  However, it would
make just as much sense for there to be no "Save changes?" prompt when
closing the window.
Comment 6 QA Administrators 2019-10-07 03:03:17 UTC Comment hidden (obsolete)
Comment 7 Terrence Enger 2019-10-12 23:07:35 UTC
I still see the bug in bibisect-linux-64.4 repository source hash
52cda5c5, 2019-10-07, running on debian-buster.
Comment 8 QA Administrators 2021-10-12 03:53:41 UTC Comment hidden (obsolete)
Comment 9 Terrence Enger 2021-11-11 16:28:40 UTC
I still see the problem in a local build of commit 631aa911
(2021-11-09), built and running on debian-buster.
Comment 10 QA Administrators 2023-11-12 03:13:14 UTC
Dear Terrence Enger,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team