30 Nov
2010
30 Nov
'10
4:50 p.m.
Spaces are allowed in authorised values and work in practice. Special characters like '/' do not seem to work in practice. My CCODEs and LOCs that have spaces in them are properly mapped in the OPAC user interface description of a book. The authorised value contains spaces but are accurately mapped to the corresponding description string. The same is not true for special characters. The same test fails. Pete. -- View this message in context: http://koha.1045719.n5.nabble.com/SQL-field-lengths-tp3285076p3286353.html Sent from the Koha - Discuss mailing list archive at Nabble.com.