Description: After setting a FK field to unique via SQL command, the relationship graph still shows up a one to many relationship between my two tables. https://ask.libreoffice.org/en/question/228432/one-to-one-relation-relationship-graph-does-not-show-up/ https://ask.libreoffice.org/fr/question/228412/graphe-de-relation-ne-montrant-pas-une-relation-11/ Steps to Reproduce: 1.create two tables with a PK in each one 2.create a FK in one table 3.set the FK to unique with SQL command to create a one to one relationship between the two tables 4.consult the relationship graph that shows a 1,N relation instead of a 1,1 relation Actual Results: the relationship graph shows a 1,N relation instead of 1,1 relation Expected Results: The relationship graph should shows up a 1,1 relation Reproducible: Always User Profile Reset: Yes Additional Info: The relationship graph shows up a 1,N relation
Please add an example and a description, which could be followed step by step. Special the SQL-code ... Note: A one-to-one relationship is a relationship, which will connect the primary-keys of the two tables. You have to set the relation from the table, which should contain all key-values, to the table, which should contain only some key-values. If you create a connection from a PK to a FK it will always be seen as 1:n, because there will be rows in the second table without any connection to the first, because the FK could be NULL.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Dear Claude Thomassin, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Claude Thomassin, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp