Make user names behave according to SQL identifiers rules [CORE4811] #5109
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
|
Commented by: @AlexPeshkoff Improvement cause some minor incompatibilities with previous firebird versions, first of all in CREATE DATABASE statement. Historically ISQL accepted USER's parameter as quoted string. Currently one can use for a traditional latin-name user with all upper letters any form of SYSDBA / sysdba / 'SYSDBA' / "SYSDBA", but an attempt to use 'sysdba' or "sysdba" remaining syntactically correct will cause an invalid login or password error. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Beta 2 [ 10586 ] |
Modified by: @AlexPeshkoff |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: Done with caveats Test Details: Implemented only simplest case: both user login and role contains only ASCII characters, though with mixed case. |
Modified by: @AlexPeshkoff |
Modified by: @AlexPeshkoff |
Submitted by: @AlexPeshkoff
Relate to CORE4820
Relate to CORE3717
Is related to CORE4864
According to the results of the discussion in firebird developers list it was decided to make user names (logins) to behave like the rest of SQL identifiers - particularly, quoted identifier is case-sensitive. When passed in DPB also as case-sensitive are treated identifiers, containing non-ascii (code > 0x7F) symbols, because in other places such names are always quoted and therefore case-sensitive.
Commits: 8c767ad 0f430b4 3fc04a9 77f6054 8d645cd 1b6632a FirebirdSQL/fbt-repository@815e42f FirebirdSQL/fbt-repository@12e519c FirebirdSQL/fbt-repository@5a28f25 FirebirdSQL/fbt-repository@081022c FirebirdSQL/fbt-repository@e5d7ac4 FirebirdSQL/fbt-repository@fd57bb9 FirebirdSQL/fbt-repository@cb62ece
====== Test Details ======
Implemented only simplest case: both user login and role contains only ASCII characters, though with mixed case.
More complex testing will be implemented after FB will allow to use non-ascii logins - currently get 'gsec error'.
Wait for reply from Alex, letter 11-jun-2015 22:01 (subj: "About 'fixed CORE4760'...")
The text was updated successfully, but these errors were encountered: