On 05/04/15 18:08, Dimitry Sibiryakov wrote: > 04.05.2015 16:41, Alex Peshkoff wrote: >> Just to notice - in that case creating quoted ascii users becomes almost >> no sense. It will be almost unreal to use them later. > The same for quoted role names.
Yes. And BTW I have a private bug report from Pavel that he can't use cyrillic roles. Sometimes can - but unstable. In his samples I sometimes see something like "'RussianRoleName'". Almost sure the problem is with that quoting and upper/lower case. >> Well, the main raised problem is why should ascii/non-ascii objects be >> treated differently? Am I understanding a problem correctly? > From the beginning of the thread I was sure that this is about following > of SQL > standard. Now I'm not sure. > To be precise - SQL standard was broken when I've added user management from SQL in 2.5. If one types: SQL> create user "Qq" password 'zz'; user QQ will be added. Telling true I've just emulated gsec behavior. So before returning to national characters let's decide - should this behavior be changed in FB3? User with what name should be created - Qq or QQ? ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
