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. >> 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. You can quote them in DPB, but not in command line. That's why I suggest to thread _ASCII_ user names not starting from digit that coming from command line to be always case insensitive. -- WBR, SD. ------------------------------------------------------------------------------ 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
