There seems to be some confusion over internal database sort sequence versus what happens in internal storage & presentation of data...
Most sensible people who design very large databases / warehouses for a living (eg sadly me) will insist that the database is implemented with case-insensitive sort sequence. The data still comes out capitalised the way you put it in / want it it to look...but the SQL just works the way a human being thinks... so if you have BOWIE and Bowie as tags, they will be treated in result sets, indexes etc as the same thing, but will appear exactly the way they were entered - they are not normalised on output (or input) unless you explicitly put them through some normalisation logic. There is NO reason for using case-sensitive SQL/databases - it just doesn't make sense. In the real world, David Bowie and DAVID BOWIE are indeed the same thing. There is no identification schema that relies on case to distinguish between (otherwise) valid identical entries for the very good reason that they simply would not work in practice. The biggest problem is that most db suppliers install "out-of-the-box" as case-sensitive...WTF do they do that?. I've asked SYBASE, Oracle etc over the years and they just look slightly embarassed...but they still don't fix a simple config option. I estimate the additional development costs of this stupidity as "the net worth of Bill Gates and then some"...all that code to "upper" this or "ucase" that etc...plus all the stupid case-related typo's...AAAAAAAAAaRRRGGGGHHHH! (rant over) However, having got that off my chest...are you SURE that the SlimDB is case sensitive? -- Phil Leigh ------------------------------------------------------------------------ Phil Leigh's Profile: http://forums.slimdevices.com/member.php?userid=85 View this thread: http://forums.slimdevices.com/showthread.php?t=24093 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
