Commented by: @paulvink

Grant, what made you conclude that SYSDBA had not been created?
You also did not mention which version of Firebid you installed.

In general, if you don't know / don't understand what's going on, it's better to ask for help on the support list first before opening a tracker item that may be unnecessary or misplaced.

Commented by: Grant Scott (disorder_cleric)

Right I was using the new beta version. 2.5.1

That is why I put the bug in the documentation section. However, at that point I had nothing to compare to. It was then that a realized that it was a non-production release. So I installed the 2.1.2 version.

Anyway the point of the bug was this if I type exactly as the documentation describes

SQL> CREATE database 'c:\database\test.fdb' page_size 8192#⁠
CON> user 'SYSDBA' password 'masterkey';#⁠
Statement failed, SQLSTATE = 28000
Your user name and password are not defined. Ask your database administrator to set up a Firebird login.

For the record c:\database does exist and has files in it.

However if I type it without the #⁠ it seems to work. You can probably downgrade the importance of this issue. I work in QA it was the first thing I noticed.

Commented by: Grant Scott (disorder_cleric)

While we are on the subject I would like to volunteer to help test this product. How does one sign up for testing? Do you just pick a task and then complete it or is there a formal procedure?

Commented by: @paulvink

The #⁠ means "Hits Enter" here. It is actually an Enter-key mark, as you can see in the HTML version:

http://www.firebirdsql.org/manual/qsg2-databases.html#qsg2-databases-creating

But unfortunately, it turns out as a #⁠ in the PDF build. At its first occurrence, under "Connecting with isql", there is a note saying: In the following examples, #⁠ means "hit Enter".

However, if you jump directly to "Creating a database using isql", you miss that note. I have now duplicated it, so that in future versions of the Quick Start Guide it will also show up under "Creating a database using isql".

As for testing: you can always test beta and RC versions and report issues to the appropriate list (for the Firebird database engine, that's firebird-devel) and/or in the tracker. If you want to get more deeply involved in Firebird QA, I suggest you start by reading http://www.firebirdsql.org/index.php?op=devel&sub=qa

Commented by: @paulvink

Duplicated note in QSG about "#⁠" showing up in PDF build.