Re: [Gnumed-devel] Upper case / lower case data storage discussion & decisions

[Karsten Hilbert]

> Just wondered whether there had been any discussion or decision to 
> force case into upper or lower for storage
> (especially for any key fields),
That would make sense. However, I am not aware of any key
fields in the current schema. OTOH it is probably rather
arbitrary whether upper or lower case is enforced for such
fields since that is what the very decision to enforce
either one means: It doesn't matter.

> or whether to permit mixed case therefore having to 
> compensate in the code for indexes and searches.
Why, of course.

> Would we ever want code to translate into "proper" case for example in 
> name fields and maybe address fields, and must these be able to be 
> over-ridden for example the dutch "van" and "de" and the german "von" ?
Huh ?  We won't be messing with what the user decides to store
apart from maybe warning about oddities. Name searches are
already taking mixed case into account, see
client/business/gmPatient.py::cPatientSearcher_SQL()

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346