To reproduce the problem :- Step 1. Create table TestTable with 3 fields:- Field Name Field Type AutoValue Entry Required Key Integer Yes - A Text - Yes B Text - No Step 2. Create form TestForm from all fields in TestTable with arrangement “Columnar – Labels Left”. Step 3. Edit the form so that “Input Required” for field B is “No”, but leave “Input Required” for both other fields as “Yes”. Step 4. Use the form to try to enter data for a new record but only enter text into field B. When attempting to save the record, this results in a message saying :- Error writing data to database Input required in field ‘A’. Please enter a value. Step 5. Select “OK”, enter text into field A, then attempt to save the record again – this will succeed. Step 6. Without dismissing the form, select the “New Record” icon to redisplay a blank form. Repeat step 4. This time, attempting to save the record results in a different message saying :- Error inserting the new record Attempt to insert null into a non-nullable column: column: A table: TestTable in statement [INSERT INTO “TestTable” (“B”) VALUES (?)] The second error message is inconsistent with the first error message. Repeating the first error message would be far more user-friendly.
So my guess is that the first error message is generated from the form properties, and the second from the insert statement. From the description, it appears that the form property constraints are ignored when you switch to a new record entry, and then the SQL parser throws an error.
Confirming on LO 4432 OSX 10.10.3
Couldn't this be the same as described in bug75340 and bug75341?
(In reply to robert from comment #3) > Couldn't this be the same as described in bug75340 and bug75341? Sure looks like it, I'd go for 75340
*** This bug has been marked as a duplicate of bug 75340 ***
Since I can reproduce this one with LO Debian package 5.0.2 and with master sources updated today but not tdf#75340 (see my last comment here: https://bugs.documentfoundation.org/show_bug.cgi?id=75340#c13), I put this one to NEW again.
Still present lib LibreOffice 5.1.1.3
Still present in LibreOffice 5.1.3.2
** 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.4.1 or 5.3.6 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-20170901
Still present in LibreOffice 5.4.1 (Windows 10 64bit)
** 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
Bug still exists in LO Version: 6.1.0.3 Build-ID: efb621ed25068d70781dc026f7e9c5187a4decd1 OpenSUSE 15, 64bit rpm Linux.
Code pointer: 3734 if ( !rColInfo.xFirstControlWithInputRequired.is() && !rColInfo.xFirstGridWithInputRequiredColumn.is() ) 3735 continue; https://opengrok.libreoffice.org/xref/core/svx/source/form/formcontroller.cxx#3734 First time, when message is comes from the form, !rColInfo.xFirstControlWithInputRequired.is() = false and !rColInfo.xFirstGridWithInputRequiredColumn.is() = true Second time, when message doesn't come from the form, obviously !rColInfo.xFirstControlWithInputRequired.is() = true and !rColInfo.xFirstGridWithInputRequiredColumn.is() = true
Tested with LibreOffice 3.3.0. Exactly the same symptoms as described in the original bug report are exhibited using 3.3.0, so set version to "Inherited from OOo"
I submitted this patch on gerrit: https://gerrit.libreoffice.org/#/c/60059/
Julien Nabet committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=d80b3235cc106e17a0c10dea44e8afa8db724400 tdf#91837: fix deinitializeControls (forms) It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Backports waiting for review in gerrit 6.1: https://gerrit.libreoffice.org/#/c/60065/ 6.0: https://gerrit.libreoffice.org/#/c/60066/
Julien Nabet committed a patch related to this issue. It has been pushed to "libreoffice-6-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=c9d15d30b66102aff3f3e10bb8243edf2ab77334&h=libreoffice-6-1 tdf#91837: fix deinitializeControls (forms) It will be available in 6.1.2. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Just for information, since analyzing consequences of the patch on 6.0 may take some time and 6.0 branch will be soon EOL , the fix won't be backport on it.
I can confirm that the error has been corrected in LibreOffice 6.1.2.1 (Windows 10 64-bit). Thanks Julien
Thank you Alan for your feedback, let's put this one to VERIFIED then.