On 05/04/15 17:22, Dimitry Sibiryakov wrote: > 04.05.2015 16:14, Alex Peshkoff wrote: >> On 05/04/15 16:39, Dimitry Sibiryakov wrote: >>> By the standard there are following cases: >>> >>> 1. An identifier contain letters [A-Z0-9_$]. >>> 2. An identifier contain letters [a-z0-9_$]. >>> 3. An identifier is starting from a digit. >>> 4. The rest. >>> >>> Case 1 is to be case-insensitive. >>> Cases 3 and 4 are to be case-sensitive. >> What? In operator: >> create table AlpHa(Beta int); >> AlpHa and Beta are case-sensitive? > How do you read that? This is case 2, not 1 or 3-4.
No. 'A' (first letter in AlpHa) does not satisfy regular expression [a-z0-9_$]. I.e. according to your words that's case 4. > >>> Case 2 is in doubts. > Without surrounding quotes it is case insensitive. > >> Stop. I did not break SQL standard - logins were not SQL identifiers in >> firebird initially, whatI;ve done is added SQL management for them. > You broke it when considered non-ascii names to be case insensitive. > >> Logins were ASCII initially, and they always were case-insensitive. >> I.e. we can start with forgetting about national characters and try to >> decide - how should ASCII identifiers be handled: according to SQL rules >> or keeping our old behavior. > Without non-ascii characters it is as said: they are case-sensitive while > quoted. I.e. when using operator create user "Alex" .... user should be created in case-sensitive form? Alex, not ALEX? That's good from SQL standard POV. The only problem that it's very inconvenient for non-ascii users. I believe people who created standard just forgotten to take into an account there needs. And some existing de-facto windows solutions. > You > can quote them in DPB, but not in command line. I can quote them in command line too :-) Not sure that users would love to use such command lines. > That's why I suggest to thread _ASCII_ > user names not starting from digit that coming from command line to be always > case > insensitive. > Just to notice - in that case creating quoted ascii users becomes almost no sense. It will be almost unreal to use them later. Well, the main raised problem is why should ascii/non-ascii objects be treated differently? Am I understanding a problem correctly? ------------------------------------------------------------------------------ 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