https://bugs.documentfoundation.org/show_bug.cgi?id=120353
--- Comment #14 from [email protected] ---
So I, and presumably large numbers of other people, will have to check every
single field, on every single form and subform because a very long-standing bug
has been fixed that we didn't know about?
Gulp. That's going to be a heck of a lot of work. I've many tens of forms and
many tens of subforms in my 2 main applications that used to work, mainly based
on database optional/mandatory settings and sometimes database default values
(so a form field can be omitted but a default set from the database).
Are you all quite sure that this is what is required by everyone?
It's also a bit strange to me that the behaviour I saw was:
6.1.2 insisted fields be filled in due to "Error writing data to database"
6.1.3.0 of 5/10/18 then worked OK for me
6.1.3.0 of 8/10/18 and subsequent versions insist that fields that are optional
in the database be filled in and still claim that there is an "Error writing
data to database", not that a field on the form has 'input required', which is
not the same thing at all.
I have to say I'd expect the mandatory/optional status of a database field
would override anything set on the form, or at least be given the option to
allow this.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
