Sprachstruktur 22 Syntax ::= | <single-line comment> ::= /* [ …] */ <single-line comment> ::= -- [ …] [ESCAPE ] ::= an SQL regular expression ::= a single character SIMILAR TO findet eine Zeichenkette anhand eines Regulären Ausdruck-Musters in SQL (engl | | | <single-value-subselect> | | any other expression returning a single value of a Firebird data type or NULL } Chapter 6.

meet the requirements for regular identifiers in other ways. ◦ All strings must be delimited with single quotes (apostrophes). ◦ Generator values are stored as 64-bit integers.  Use of Dialect 3 is block and in-line. Syntax ::= | <single-line comment> ::= /* [ …] */ <single-line comment> ::= -- [ …] -38 to 3.402 * 10 38 Single-precision IEEE, ~7 digits FLOAT (bin_prec) 32 bits or 64 bits bin_prec binary precision Binary precision 1 - 24: synonym for FLOAT (32-bit single precision) 25 - 53: synonym

meet the requirements for regular identifiers in other ways. ◦ All strings must be delimited with single quotes (apostrophes). ◦ Generator values are stored as 64-bit integers.  Use of Dialect 3 is block and in-line. Syntax ::= | <single-line comment> ::= /* [ …] */ <single-line comment> ::= -- [ …] digits, reliable size depends on the platform FLOAT 32 bits 1.175 * 10 -38 to 3.402 * 10 38 Single-precision IEEE, ~7 digits INTEGER, INT 32 bits -2,147,483,648 up to 2,147,483,647 Signed long

in the following sections. The database name is the name of the primary database file which for a single file database is simply the database name and for multi-file databases, it is the first data file for it -n(o_update) read-only validation (-v) -o(nline) database online <single / multi / normal> -pr(ompt) prompt for commit/rollback (-l) -pa(ssword) dialect n -sw(eep) force garbage collection -sh(utdown) shutdown single / multi> -tw(o_phase) perform automated two-phase recovery -tra(nsaction) shutdown

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Single File Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1. Introduction 2 Chapter 2. Database Structure When you create a new database, be it single or multiple file, a number of things happen: • The database file(s) are created; • The header page pages) for the system tables, indices and the various database overhead pages. 2.1. Single File Databases A single file Firebird database consists of a number of pages, each the same size, and all held

connec- tion, each with its own cache. Less re- source use if the number of connections is low. Single server process with a separate thread for each connection. Shared cache space. More efficient if network cards, and they are different, you can simply use those. • If you are intending to try out a single-machine installation of both client and server, you should use the local loopback server address is not a TCP/IP connection and it is not a thread-safe way to connect to a local server. For using single instances of the command-line tools (gsec, gbak etc.) it works just fine. By contrast, direct database

SuperClassic and SuperServer mode. What are they? • Classic mode (aka MultiProcess) involves a single listening process that spawns off an additional process for each client connection. Using a locking mechanism, it allows shared connections to database files. • SuperClassic (ThreadedShared) is a single server process. Client connections are handled by separate threads, each having their own database (hence the Shared). • Superserver (ThreadedDedicated) is also a single server process with threads handling client connections. There is a single, common database page cache. The server requires exclusive

client connection, each with its own cache. Less resource use if the number of connections is low. A single process serves all connections, using threads to handle requests. Shared cache space. More efficient Start 11 Installing multiple servers Firebird 2 allows the operation of multiple servers on a single machine. It can also run concurrently with Firebird 1.x or InterBase servers. Setting this up is enough access rights. Note You can optionally enclose the path, the user name and/or the password in single (') or double (") quotes. If the path contains spaces, quoting is mandatory. At this point, isql

you should use them. It is an attempt to collect all relevant information about generators in a single document. 1.2. Who should read it? Read this article if you… • are not familiar with the concept or 0 for all those you created. Now let’s have a look at the RDB$GENERATORS table, here with a single self-defined generator: RDB$GENERATOR_NAME RDB$GENERATOR_ID RDB$SYSTEM_FLAG RDB$SECURITY_CLASS available in one database? Since Firebird version 1.0, the number of generators you can have in a single database is limited only by the maximum assignable ID in the RDB$GENERATORS system table. Being

a previous restore failed due to data errors. Normally, a restore takes place in a single transaction with a single commit at the end of the restore. If the restore is interrupted for any reason, an empty change the SQL Dialect using gfix. Under normal circumstances, restoring a database takes place as a single transaction. If the restore is successful, a commit at the end makes the data permanent, if not the above that the password doesn’t show up under Firebird 2.1 as each character is replaced by a single space. This does mean that it is possible for someone to work out how long the password could be