Jim Starkey wrote:

> Here is an updated version of the RDB$USERS tables implemented by Vulcan:
>
> static const char *creationDDL [] =
> {
> "create domain rdb$user_name varchar(128) CHARACTER SET
> UNICODE_FSS;",

Porting given version of RDB$USERS into fb2, I've found a little problem
(not bug, but something contra-intuitive).
We already have
create domain rdb$user varchar(31) CHARACTER SET UNICODE_FSS;
Domain rdb$user is used in rdb$ relations, procedures, roles and
privileges. Creating rdb$user_name together with already existing
rdb$user (with same functionality - store user's name) seems strange to
me. Why not use already existing one?
I can find only one excuse for this duplication - it makes formally
possible to use old ODS security database ODS 11 with newer (ODS 12 or
13?) databases, that handle SQL identifiers according to standard. But
this will definitely require new version of authentication plugin
'security database'. Do we really need to be able to support new version
of plugins with old databases?