. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.5. Database information request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.7. Transaction information request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Table of Contents 1 5.10. Information request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634 Appendix A: Supplementary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firebird 4.0 version, the Firebird 3.0 Language Reference was taken as the base, and Firebird 4.0 information was added based on the Firebird 4.0 Release Notes and feature documentation. 1.2.1. Contributors language features that differ from Dialect 3, the default for Firebird databases. ◦ Date and time information are stored in a DATE data type. A TIMESTAMP data type is also available, that is identical to

.................................................................................... 5 Embedded Server for Windows .................................................................................... ...................................................................... 9 Installing the Firebird server ................................................................................................ ............................................................................................. 14 Server configuration and management ...................................................................

code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. Embedded Firebird Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . database it must connect to the Firebird server process. On receiving a connect request the server process will authenticate the user credentials against the server users defined in the security database database. If authentication is successful the server will allow the application access to any database that it requests and then use the roles and privileges defined in that database to provide fine-grained

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Appendix A: Supplementary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . in comparison to the data manipulation language (DML) employed for queries and the PSQL used for server-based programming. The leader of the Firebird Project’s documentation team, Paul Vinkenoog, took language features that differ from Dialect 3, the default for Firebird databases. ◦ Date and time information are stored in a DATE data type. A TIMESTAMP data type is also available, that is identical to

distributions put it in /etc/firebird/n.n where n.n is the version of the Firebird database server. There is more information on connecting to databases, using full paths or aliases, below. Chapter 3. Invoking -x extract metadata -z show program and server version Not all of these switches appear in every release of Firebird. Some will be seen in more Command Line Switches 7 When the server provides line and column information, users can see the exact line of the DML in the script that caused the problem. When the server only indicates failure, users

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. Installing the Firebird server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.2.4. Server modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pinging the server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.4.2. Making sure that the Firebird server is running

............ 8 Pinging the server ...................................................................................................... 8 Checking that the Firebird server is running ................ ................................................................... 11 A network address for the server ............................................................................... 11 Default user name database .................................................................................... 13 Server name and path ..................................................................................

command (or an invalid command), or with the -⁠? switch, results in the following screen of helpful information: gfix usage instructions for Firebird 3.0.7 usage: gfix [options] plausible options utility which was executed with a password on the command line could result in other users of the server seeing that password using a command like ps -efx | grep -i pass. From Firebird 2 onwards, this code is always zero — at least up until Firebird 2.0.  When logging into a database on a remote server, you will always be required to pass the -⁠u[ser] and -⁠pa[ssword] parameters. Chapter 3. Gfix

-V[ERIFY] Normally gbak operates quietly with no information written to the display. This switch reverses that situation and causes lots of information to be displayed. The default is to display the output device, rather than the screen, or to suppress them altogether. If -y suppress is used, then no information will be written to screen regardless of whether -v[erify] is specified. If a filename is given log -v gbak:cannot open status and error output file employee.log -Z This option displays some information about the version of gbak being used, and optionally, a database. To obtain the version of gbak