On Thu, Jan 13, 2011 at 11:23:01AM -0500, Yannick Warnier wrote: > > Currently, for example, the "search" functionality doesn't return > > anything unless you exactly match the case of the thing you're looking > > for, which is not very userfriendly. [...] > > In terms of usability, search features should *always* be case > insensitive by default, and a checkbox should allow you to make the > search case-sensitive. > > Web users today (and particularly the public at large to which we are > referring) are not trained to even understand what case sensitivity is, > so it implies too much effort (in comparison with the results we could > hope for) to force them to use "the right thing".
Agreed, and this is also the point I was trying to make. > This being said, at the developer level (field names and that kind of > stuff), we *must* be super-strict, otherwise we'll end up with an > unordered situation as we have now in 1.8. That's why it's a good idea to set everything to case sensitive in MySQL, and explicitly use case-insensitive operators. This will make everything work as intended. And it will also make things insensitive in PostgreSQL, which is currently not the case. Cheers, Peter Bex Solide ICT - http://www.solide-ict.nl _______________________________________________ Dev mailing list Dev@lists.chamilo.org http://lists.chamilo.org/listinfo/dev
