You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If allow_null is set to 0 for a field (e.g. in cfg/cfg.d/eprint_fields.pl) then when the database is created (in MariaDB 10,5 but possibly also earlier versions of MariaDB 10) the table has an inconsistency which prevents new data objects (e.g. eprints) being created with the following error:
Field 'myfield' doesn't have a default value at /opt/eprints3/perl_lib/EPrints/Database.pm line 1389.
The text was updated successfully, but these errors were encountered:
There seems to be no good reason for allow_null as a field attribute if you cannot also set the default to be defined with the table structure. Although defaults can be set in eprint_fields_default.pl, these don't look to be passed through to the table structure and they would likely cause hassle even if they did, as it would be difficult to subsequently update the default.
If allow_null is set to 0 for a field (e.g. in cfg/cfg.d/eprint_fields.pl) then when the database is created (in MariaDB 10,5 but possibly also earlier versions of MariaDB 10) the table has an inconsistency which prevents new data objects (e.g. eprints) being created with the following error:
Field 'myfield' doesn't have a default value at /opt/eprints3/perl_lib/EPrints/Database.pm line 1389.
The text was updated successfully, but these errors were encountered: