https://bugs.documentfoundation.org/show_bug.cgi?id=120245
--- Comment #4 from Lionel Elie Mamane <[email protected]> ---
This most probably comes from the fix of bug 75341.
First thought: What we should do is check whether the column has a default
value set, and in this case accept that the form gives no value. But:
1) This will not work with PostgreSQL-sdbc because the driver doesn't quite
implement reading/setting default values.
2) This is still not 100% correct; there may be a more subtle mechanism that
makes not giving that column a value acceptable, although it is "NOT NULL" e.g.
an INSERT trigger that will put a value, but no "default value" attached to the
column.
So LibreOffice shouldn't try to double-guess the database. Just throw the
values entered by the user, and let the database return an error if needs be.
The form designer can always require a value with a validator, with having the
control's "value required" property set or with a beforeUpdate macro.
Julien, please remove the "&& && rColInfo.nNullable != ColumnValue::NO_NULLS"
from the commit that fixed bug 75341 completely. Thanks.
--
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
