Creating a digital object without path raises an error in 2.5.x
|Assignee:||Dan Gillean||% Done:|
|Target version:||Release 2.5.2|
|Google Code Legacy ID:||Tested version:||2.5|
- Perform a metadata only DIP upload from AM.
path column from DO table has a
NOT NULL clause without a default value. This is causing MySQL errors when the DO is created from the metadata only DIP upload request (I think it's the only place for now), where the DO has an "Offline" usage and no path.
This issue came out now probably because of the upgrade to MySQL 5.7 and/or the re-addition of
STRICT_TRANS_TABLES to the
sql_mode. Options to fix it:
1. Remove the
NOT NULL clause or add a default value to the column (requires migration).
sql_mode (less secure database and requires documentation and deploy changes).
3. Make sure
path is not
NULL on DO save.