Tested w/ Ubuntu 11.04, Lbo 3.5 RC2, Postgresql 8.4 Open an ODB connected to a postgresql database with muliple relationship constraints. Open the relation design window. Not all relationships will be displayed - in testing this was true 100% of the time the first time that window is opened. But if you do anything to that makes LibO think the window contents should be saved (even if you just trick it) and do so, then close the window and reopen it, most of the time (sorry it is not all the time) it then picks up the other relationships. This seems to be limited to the relation design window as the Query designer and/or wizard and form wizard pick up all of the relationships right fro the start.
Thanks for bugreport Please, attach small database with which this bug reproducible. Or add link where it can be downloaded. May be test databases for Postgresql exists, tell if so. Also attach odb file that demonstrates this problem.
Drew, I can confirm similar behaviour with regard to the native mysql connector extension and a mysql server. The problem appears to indeed lie with the Relationship designer tool/dialog. In my own case : - dragging and dropping to create a relationship between two tables appears to work, but only once between any two tables - in reality, the relationship is not created, the graphical UI representation always default to the first entry in the first table's field list, and if you click on the link to edit the relationship displays only one half, as it turns out the second table to which the link was made without referencing any field from the first table !!! - trying to manually create a relationship by clicking on the Define button allows one to choose the fields from the tables to be linked, but when validated, fails to do this correctly, i.e. we get a repeat of the scenario above, whereby only the first field of one table appears, and this link only includes one field from one table, and not even the one that was defined by the user !!! The whole relationship design tool/dialog seems broken, at least for external db's, I haven't tried with hsqldb internal. Alex
Confirming as reproducible on LibreOffice 3.5.5.3 Mac OSX 10.7.4. Test database : XTuple (http://www.xtuple.com/free-demo-of-xtuple-erp) Using the built-in connector, when I call Tools > Relationships, the window opens but does not bring up any of the predefined relationships in the database. I get a Table list window, asking me to add the tables to define the relationships I want. Compare the above behaviour to the same database, using a postgres JDBC connector: - the relationships are displayed, in fact, so many of them that they overlap each other within the window (but that is not a new problem as such, it has always been that way, independent of the underlying database). Conclusion : it works in with JDBC and not with sdbc-postgres. Alex
Confirmed on NEWER 4.1.0.4. The problem is the same. Sometimes the relationships are correctly, sometimes not. I've over 30 tables with Postgresql. Opening, closing, reopening... and some relationships appear and disappear. No changes from the psql console: the CONSTRAINT values is not altered.
Adding self to CC if not already on
Changing title because the problem is independent of db engine
*** Bug 88033 has been marked as a duplicate of this bug. ***
Alex/Drew: I put it at NEEDINFO, waiting for your feedback about this tracker.
(In reply to Julien Nabet from comment #8) > Alex/Drew: I put it at NEEDINFO, waiting for your feedback about this > tracker. What information do you need ? The duplicate report bug 88033 contains a sample document and screenshots explaining and showing the problem.
(In reply to Alex Thurgood from comment #9) > (In reply to Julien Nabet from comment #8) > > Alex/Drew: I put it at NEEDINFO, waiting for your feedback about this > > tracker. > > What information do you need ? > > The duplicate report bug 88033 contains a sample document and screenshots > explaining and showing the problem. In bug 88033, the bug was reported against LO 4352, I confirmed on master Version: 4.5.0.0.alpha0+ Build ID: 6143a7eeabea394133c54e97e3690bdf40b98247 Locale: fr_ on OSX 10.10.2
Alex: Sorry, had missed information from tdf#88033, I'll take a look, thank you! :-)
Ok, I reproduced the bug. In fact, it seems that only 1 relation is possible between 2 tables. Indeed, if I remove link between "tbl_product" and "tbl_bug" then add another one, it's ok. I noticed too that when trying to create second relation, cardinality doesn't appear. Perhaps both behaviors are linked.
I'm lost by the number of parts involved: dbaccess/source/ui/control/RelationControl.cxx svtools/source/brwbox/editbrowsebox.cxx svtools/source/brwbox/brwbox1.cxx ... example of bt: #0 dbaui::ORelationControl::getColumnIdent (this=0x2fb5c90, _nColId=65535) at /home/julien/compile-libreoffice/libreoffice/dbaccess/source/ui/control/RelationControl.cxx:274 #1 0x00002aaad025c15d in dbaui::ORelationControl::InitController (this=0x2fb5c90, nRow=0, nColumnId=65535) at /home/julien/compile-libreoffice/libreoffice/dbaccess/source/ui/control/RelationControl.cxx:305 #2 0x00002aaaafbd8b73 in svt::EditBrowseBox::ActivateCell (this=0x2fb5c90, nRow=0, nCol=65535, bCellFocus=true) at /home/julien/compile-libreoffice/libreoffice/svtools/source/brwbox/editbrowsebox.cxx:1027 #3 0x00002aaaafbda5c1 in svt::EditBrowseBox::ActivateCell (this=0x2fb5c90) at /home/julien/compile-libreoffice/libreoffice/include/svtools/editbrowsebox.hxx:571 #4 0x00002aaaafbd888d in svt::EditBrowseBox::CursorMoved (this=0x2fb5c90) at /home/julien/compile-libreoffice/libreoffice/svtools/source/brwbox/editbrowsebox.cxx:987 #5 0x00002aaaafbac049 in BrowseBox::GoToRow (this=0x2fb5c90, nRow=0, bRowColMove=false, bKeepSelection=false) at /home/julien/compile-libreoffice/libreoffice/svtools/source/brwbox/brwbox1.cxx:1544 #6 0x00002aaaafbaaa01 in BrowseBox::RowInserted (this=0x2fb5c90, nRow=0, nNumRows=2, bDoPaint=true, bKeepSelection=false) at /home/julien/compile-libreoffice/libreoffice/svtools/source/brwbox/brwbox1.cxx:1243 #7 0x00002aaad025b694 in dbaui::ORelationControl::lateInit (this=0x2fb5c90) at /home/julien/compile-libreoffice/libreoffice/dbaccess/source/ui/control/RelationControl.cxx:187 #8 0x00002aaad025e3cc in dbaui::OTableListBoxControl::lateInit (this=0x2fadd40) at /home/julien/compile-libreoffice/libreoffice/dbaccess/source/ui/control/RelationControl.cxx:673 Value of nCol seems strange but I can't succeed in understanding the whole mechanism, too messy!
(In reply to Julien Nabet from comment #13) > Value of nCol seems strange This looks like the special value "unknown/invalid column": include/svx/gridctrl.hxx:#define GRID_COLUMN_NOT_FOUND SAL_MAX_UINT16
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.0) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
LO-5.0.3.2 CentOS-6.7 Bug remains in this version. When attempting to add relationships from multiple fields in one table to the primary key of another relationships added subsequent to the first generate an error and cause a relationship editing window to appear. If the multiple relationships (T2.field1 -> T1.id, T2,field2 -> T1.id, T2.field3 -> T1.id) are entered manually in the relationship editing window then LO crashes and the recovery shows no trace of the previously attempted work.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
I still see the bug with debian stretch running daily Linux dbgutil bibisect repository version 2017-04-15 with an embedded Firebird database. I have the example .odb and STR, but I think they do not add much to what is already here.
*** Bug 101230 has been marked as a duplicate of this bug. ***
(In reply to Terrence Enger from comment #18) > I still see the bug with debian stretch running daily Linux dbgutil > bibisect repository version 2017-04-15 with an embedded Firebird > database. > > I have the example .odb and STR, but I think they do not add much to > what is already here. About Firebird, it's been fixed with https://cgit.freedesktop.org/libreoffice/core/commit/?id=d499cb3bd585e9fcc21bc586cad3d2ad2487a451 for tdf#107196 For other databases any better with recent LO version? (last stable one is 5.3.4)
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Drew Jensen, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Drew Jensen, 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 MassPing-UntouchedBug