Re: Non-case sensitive queries

In article <2p3u3l$jg9@msuinfo.cl.msu.edu> decello@discovery.uucp (Joseph P DeCello III) writes: [...] > > What if I enter "Joseph P DeCello III", your program would change it to: > Joseph P Decello Iii > > this is undesirable. The same applies to John von Neumann or Jeanne d'Arc as well. But this is not the point, I guess. But, if John von Neumann, AND the appropriate normal form, say "john von neumann" are both stored in the same row, one could greatly benefit from this. We use a modified soundex algorithm to store normal forms os names beside the natural form, which unifies "Seebauer" (pronounced like Z'bower) and Sehbwr to the same entry. But the need of explictly storing something like a normal form points to a SQL drawback. Comparison, in doing searches, is restricted to the most common operators .LE.,.LT.,.EQ., and so on. Expression matching to something similar to regular expressions is also possible. General predicates are not supported. H.