|
The only way to get this right is not to lose the mixed-case form in the first place. If it's not feasible just to store the name in mixed-case and upper-case it for comparisons
To me, the only reason this data is stored in the database in uppercase is inertia. Years and years ago printers could only print uppercase. For all of you that are smarter than me: Suppose I decide I'm going to just store the data in the database in mixed-case form. What are the ramifications? Will sorts and OPNQRYF and SQL still _sequence_ them in true alphabetical order? I understand that comparisons for include/equal/etc need to be altered as "Joe" and "JOE" will not compare equal. What other kinds of thing are there? As long as Midrange-L has been here and as often as other topics have repeated themselves ad nauseum, I'm rather amazed we haven't hashed this out before. 'Course I lose brain cells on a monthly basis . . .
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.