https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633
--- Comment #73 from Nick Clemens (kidclamp) <[email protected]> --- (In reply to Andrew Fuerste-Henry from comment #72) > BUT things go weird if preferred_name is NULL -- in KTD the default data has > preferred_name null but saves new/edited patrons with a blank instead. In > the real world, I imagine patrons could be imported with a NULL value. With > NULL preferred_names I get: > > - surname: Acevedo, preferred_name: NULL, firstname: Henry > - surname: Acevedo, preferred_name: NULL, firstname: Hosea > - surname: Acevedo, preferred_name: NULL, firstname: Hank I originally thought we could simply add a default value - however, TEXT columns cannot have a default value in MySQL - MariaDB does allow this Either we need to supply the default on storing - or build and internal functions - OR make sort_name a VARCHAR, but it would be storing a longtext so would be problematic - I am not sure why name fields are longtext This may mean sort_name is a unacceptable solution -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
