> 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
