24.07.2015 16:54, Alex Peshkoff wrote: > Adriano, initially it was said that in passwords (to be precise - not > only passwords, but also logins and filenames) from CONNECT command in > ISQL we currently can use international characters, provided they are in > current OS session locale. Next Dimitry pointed out that in a script > they may be provided in another charset, referenced by SET NAMES > command. As far as I understand the discussion is about what can be done > in such case.
Let me provide an example. Say, Pavel Cisar has a script that connects to a database with Czech symbols in name using Czech user name and password. This script is in cp1250 and works perfectly well on his computer. Now, he sends the script to me and ask me to run it. I have current locale set to cp1251 and this script will fail for sure. Using of SET NAMES inside of the script is not enough. To be able to run the script, I have to change my locale. This is not a deal big enough to make FB3 waiting, but it is a globalization issue that should be addressed somehow somewhen. -- WBR, SD. ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
