You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow statement 'create OR ALTER user sysdba password ...' to initialize empty securityN.fdb as 'CREATE user ...' (i.e. which is typed without "or alter" clause) [CORE5266]
#5545
Chapter "Initializing the Security Database" (Firebird-3.0.0-ReleaseNotes.pdf, pg 126) issues that for initializing of empty securityN.fdb one need to connect to secN.fdb using local protocol and issue then 'CREATE USER SYSDBA PASSWORD ....'.
It would be nice if command 'create OR ALTER user sysdba ...' also could work for this case.
Currently this is not so:
C:\MIX\firebird\fb40>.\isql security4.fdb
Database: security4.fdb, User: SYSDBA
SQL> create OR ALTER user sysdba password 'masterke';
Statement failed, SQLSTATE = 28000
no operation specified
-Install incomplete, please read the Compatibility chapter in the release notes for this version
SQL> create user sysdba password 'masterke';
SQL> commit;
SQL> show users;
Users in the database
2 #SYSDBA
SQL> quit;
Submitted by: @pavel-zotov
Votes: 1
Chapter "Initializing the Security Database" (Firebird-3.0.0-ReleaseNotes.pdf, pg 126) issues that for initializing of empty securityN.fdb one need to connect to secN.fdb using local protocol and issue then 'CREATE USER SYSDBA PASSWORD ....'.
It would be nice if command 'create OR ALTER user sysdba ...' also could work for this case.
Currently this is not so:
C:\MIX\firebird\fb40>.\isql security4.fdb
Database: security4.fdb, User: SYSDBA
SQL> create OR ALTER user sysdba password 'masterke';
Statement failed, SQLSTATE = 28000
no operation specified
-Install incomplete, please read the Compatibility chapter in the release notes for this version
SQL> create user sysdba password 'masterke';
SQL> commit;
SQL> show users;
Users in the database
2 #SYSDBA
SQL> quit;
PS. WI-T4.0.0.238, WI-V3.0.1.32527
Commits: 6853447 e7d88a1
The text was updated successfully, but these errors were encountered: