05.04.2016 15:53, Alex Peshkoff wrote: > But there are a lot of other places where NoCaseString is used. And it's > very efficient when case-insensitive strings are needed. It will be not > good to loose such class.
Yes. But in most of these places using of case-insensitive string is causing bugs. For example, using it in map hash not only fail now, but also is causing dangerous situation when on POSIX users from Security4.fdb can be used instead of the same users from security4.fdb and vice versa. User SySdBa also can be mixed up by engine with user SYSDBA. You know consequences. > What prevents from (for example) making them always utf-16 and > performing case-insensitive comparison for them? Too many things will be broken. Second-fresh developers are not allowed to cause regressions. -- WBR, SD. ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
