On 05/06/15 23:27, Jim Starkey wrote: > Non-ASCII, non-quoted names are a) illegal by SQL standard
Yes, illegal, but logins and roles may arrive not in SQL context. They come to server in DPB. > and b) impossible to handle by Lex without both character set declaration and > explicit language support for that character set It's anyway required to transliterate identifier to metadata charset. > , and c) a really bad ideas (in my humble opinion). Otherwise, how can lex > even parse the identifier? Assume any character it doesn't recognize is a > letter? luckily lex need not parse DPB With Dmitry's suggestiion I see no problems with that identifiers - the only difference from exact SQL is that unquoted identifier with non-ascii symbols may exist. But we always treat it as quoted one i.e. leave case unchanged. Unquoted ascii-only logins/roles from DPB are uppercased. > > If Firebird were UTF-8 only, which I think would be a good thing, maybe rules > could be relaxed. But trying to handle identifiers in random character sets > is untenable. > > > Jim Starkey > > >> On May 6, 2015, at 4:04 PM, Leyne, Sean <s...@broadviewsoftware.com> wrote: >> >> >> >>> I didn't follow all the details of this discussion, but this is how I see >>> the things: >>> >>> 1) I don't think non-ASCII user/role names ever worked reliably and we >>> never recommended using them. So if someone used them, they should be >>> prepared for troubles. And this is OK (more or less) during a major version >>> upgrade. Life is cruel. >>> >>> 2) Unquoted ASCII user/role names should work the same way as before. I >>> believe we support the standard here by implicitly uppercasing them. >>> >>> 3) Quoted ASCII user/role names should work as declared in the standard, >>> i.e. be case-sensitive. If this causes compatibility issues for someone, >>> well, so >>> be it. I don't think there are many of such usage cases. >> I agree with everything that you have outlined, the question which is >> resolved by these answers is: >> >> How should unquoted non-ASCII characters in user/role names be handled >> (without the requiring ICU installed at client)? >> >> >> Sean >> >> >> ------------------------------------------------------------------------------ >> 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 > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
